I recommend trying out some of your most popular workbooks, publishing some extracts, running some extract refreshes and seeing if everything appears to work the same as it used to. Given that you posted this 6 days ago, I imagine you would have seen some issues by now if anything went wrong.
Ps. For future reference, doing a performance capture before and after may be a good idea. You can also look at the admin views and see if everything is in line with where it was before.
I usually write all steps before upgrade( every single step which are needed during the upgrade). This way, i'm pretty sure not missing anything. Screenshots of the maintenance page, keys, perform a complete backup( latest instance).
I would suggest the following,
1) Create all the steps and document
2) Take a complete backup
3) backup any customizations files you might have.
4) License keys.
5) Disable all backgrounder jobs
Perform the upgrade
- Restore from the backup
- Check license keys.
- Unpause all the jobs
1) Login to the system
2) Open workbooks
3) Check maintenance page
4) Create a new schedule and run a sample job
5) Open desktop and import a workbook
6) make small change and publish it as a new workbook
7) Create an extract. Assign permissions and publish
8) Check any custom views created.
I can go on and on, but just perform some core activities that are done everyday by users and make sure they're fine.
Rest assured, if you perform the check list the upgrade should be sailing.
I'm not sure I understand step #5. When performing an update/upgrade one simply Stops the server:
Uninstalls the software:
Then install the update. There's no need to mess with Services or Processes.
Because the process doesn't delete everything there isn't a need to restore from a backup. Everything (workbooks, Groups, Schedules, etc.) will be there as before.
The reason to disable the backgrounder is to avoid triggering the backgrounder jobs right after the upgrade is completed.
When a backup is performed, tableau backup up all the required components. However, if we're restoring the backup on a new machine or existing, the backgrounder will be in pending state for any pending jobs and will try to process any missed jobs during the upgrade. These jobs will trigger right after the upgrade is done and system is available. To avoid this, we started to disable all the backgrounders and enable them back so we can choose which scheduled jobs to run.
This step is not required if there are no background jobs during the upgrade time.