While many organisations are well-served by performing an in-place upgrade of Tableau Server, other organisations with mission-critical use of Tableau may want a more robust, enterprise-grade upgrade approach which uses investments of additional effort and resources to reduce risk and impact. In these cases, Tableau recommends a “Blue/Green” upgrade approach to achieve that outcome, characterised by:

  • Reliable deployment of applications into a freshly configured host non-production environment (versus an in-place upgrade)
  • Performing pre-production testing of the new version in your non-production environment to validate business-critical functionality, including testing common use cases to detect changes in behaviour that may impact the organisation
  • Testing in production-identical environments to validate integrations and resource requirements
  • The ability to roll back to the previous version rapidly

This high-level guidance describes a Blue/Green approach to upgrades that has been successfully used by many of our biggest customers to upgrade Tableau Server (and other mission-critical applications) with confidence. Blue/Green upgrades are a long-established industry practice(Link opens in a new window); there are many variations and the specific steps below are one possible path. If you’re seeking specific guidance on customising this approach for your organisation’s next upgrade, talk to your Premium Support Technical Account Manager, or discuss a services engagement with your account executive or delivery partner.

The Blue/Green approach involves installing a new version of Tableau Server in a non-production environment (your “Green” installation) that mirrors the configuration of your existing production environment (your “Blue” installation). For purposes of your Tableau licence, note that Tableau grants a standard right to two (2) non-production environments to support the single production environment in your deployment, as further described in the governing licence agreement.

By copying your content from the production environment to the Green installation in your non-production environment, you can create an upgraded instance of Tableau Server with minimum downtime and the safety net of having the original production installation to fall back to if necessary. Once you’ve determined that all your critical content in the Green environment is functional, switch your users over to the new environment (Green). Your Green environment becomes your production environment, and your original installation (Blue environment) can be maintained as a non-production environment to support your next upgrade.

What follows is a high-level outline of the steps necessary to use Blue/Green as an approach to upgrade Tableau Server. These assume you have a load balancer or DNS that allows you to redirect user traffic from one installation to the other, and that you have downloaded the new version of Tableau you want to upgrade to.

Important: Your Blue/Green installations should be treated as production environments. They should not serve as disaster recovery or general testing environments. For more details on Disaster Recovery, please see Disaster Recovery(Link opens in a new window) in the Tableau Blueprint.

  1. Create a second installation of servers that mirrors your production installation of Tableau Server as closely as possible. This second environment is your Green installation, a non-production environment. It should have a similar capacity, resources and configuration as your production environment (“Blue”) because your Green instance will become your production instance after the upgrade.

  2. Create an initial backup of your Tableau Server Blue installation. You’ll use this for initial user acceptance testing (UAT) in Green. Later, you’ll create a final, up-to-date backup to use before actually switching from Blue to Green. For details on creating backups, see Back up Tableau Server Data.

  3. Install the new version of Tableau Server in Green. You should specify the same Identity Store type and Run As service account as you use in Blue.

  4. Restore the initial backup from Blue into Green. This creates an upgraded, mirrored version of your Blue production environment. See Restoring core Tableau Server functionality.

  5. Disable any scheduled tasks in Green to avoid sending duplicate messages while testing and to avoid overloading database resources. For details, see Server Upgrade - Disable Scheduled Tasks.

  6. Test the Green installation to confirm that it is functioning as expected. Perform User Acceptance Testing (UAT), and simulate any load testing if desired. If you have scripts or API integration with Tableau, you should test these as well. The more complete your testing, the better prepared you will be to address any discrepancies between your original Blue installation and your new Green installation.

  7. Prepare the Blue installation so you can create a backup you’ll use for production in Green. This might mean restricting access to Tableau or sending a message instructing users not to make any changes to their content and warning them that any changes made after you create your backup will be lost.

  8. Create a final backup of Blue. This is the backup you will use to bring Green up to the most recent production content. If you do regular backups, you can use your latest production backup, keeping in mind that any changes or updates done in Blue after the backup is created will be lost. We recommend a “change freeze” on your production environment after this backup is taken, so no new workbooks or data sources are added, and there are no changes to existing content.

  9. Restore the final Blue backup to Green.

  10. Perform UAT/sanity checks on Green content.

  11. Re-enable schedules for any jobs, subscriptions and notifications you disabled in Step 5 above.

  12. Switch your users to Green using a load balancer or DNS, and block access to Blue.

  13. Verify that the Green server is functional as desired and monitor for production load issues. If you have Advanced Management, you can use the Resource Monitoring Tool to monitor performance.

  14. (Optional) If you're not keeping your Blue environment for future upgrades, deactivate the Blue environment product keys:

  15. (Optional) If you're not keeping your Blue environment for future upgrades, stop the Blue environment and prepare it for decommissioning.

Thanks for your feedback!