Advance with Assist: Tableau Server Migrations

Data

Advance with Assist: Tableau Server Migrations

Advance with Assist shares quick solutions to common challenges encountered by the InterWorks Assist on-demand team.

Question: I need to migrate Tableau Server; what are my options? Should I be using something like Azure Site Recovery or AWS AMIs to move my cluster?

The Challenges

There are a few challenges to using any sort of snapshot-based technology to migrate a Tableau Server deployment, especially a multi-node deployment. This goes for Azure Site Recovery, deploying instances from Amazon Web Services AMIs, or even a Veeam Instant Recovery on-premises.

Single-Node Deployments

  • To ensure it hasn’t been cloned onto new hardware, Tableau’s licensing service looks at several identifiers, such as the network adaptor MAC address and the VM (or instance) unique identifier. Since these snapshot-based tools generate new VMs, these IDs change, and it invalidates the Tableau license activation.
  • Server hostname. If the server’s hostname changes, Tableau Server will cease to function.

Multi-Node Deployments

  • All the challenges from Single-Node, plus:
  • IP addresses. In a clustered environment, if the IP addresses of the servers change, the nodes will not be able to communicate with the TSM controller.
  • Snapshot time differences. Depending on how far apart in time the snapshots were taken across the nodes, the migrated Tableau Server may not be able to get all the processes in sync again.

The Potential Workarounds

There are workarounds for some of these, with varying amounts of pain:

  • Deactivate all Tableau Server licenses before taking the snapshot that will be used to migrate the environment. Tableau services need to be stopped during this to prevent users’ roles from being changed to Unlicensed.
  • If IP addresses will be changing, the worker nodes could be removed before the migration and re-added to the cluster after.
  • If some services fail to synchronize after the migration, a Tableau Server backup could be restored onto the migrated environment.
  • There is no workaround for hostname changes – a rebuild is required.

A Better Solution

In most cases, the best course of action is to build a new Tableau Server environment up in parallel (taking advantage of one of the two non-production environments the Tableau licenses allow) and restore in a backup. Let’s look at that process:

  1. Provision new server VMs/instances. Since you’re building fresh instances anyway, now might be a good time to evaluate if switching from Windows to Linux makes sense. Or maybe it’s time to make the leap to that new release of Tableau Server you’ve been putting off.
  2. Install Tableau Server on the new environment, matching the process topology between old and new.
  3. Migrate content and settings. Here’s Tableau’s documentation about that process.
  4. If the environments will run in parallel for a while, disable schedules on the new environment to prevent duplicate subscriptions and extract refreshes.
  5. Test out the new environment.
  6. When it’s time to switch over:
    • Restore in a fresh backup if the new environment needs to catch up with changes made to the old one during testing.
    • Re-enable schedules.
    • Point DNS or the load balancer at the new environment.

While this does require some work, all of it except the very last step can be done without downtime or impact to the production environment, unlike each of the workarounds mentioned before.

InterWorks Is Here to Help

The Assist team is always here to help. To learn more about Assist by InterWorks, check out this blog post to see how Assist can help you with your data and tech challenges. Looking for more support around licensing? Don’t hesitate to let our team know if you need help planning your next migration!

Want More Advance with Assist

  1. Advance with Assist: Filtering Select Dates with DATETRUNC
  2. Advance with Assist: Enhancing Dashboards with Custom Icons
  3. Advance with Assist: Tableau Power User Leaving the Company
  4. Advance with Assist: Context Filters and LOD Calculations
  5. Advance with Assist: Custom Subscriptions with Tableau Server Custom Views
  6. Advance with Assist: Blending with Dimension Not Utilized
  7. Advance with Assist: Creating a Sankey Diagram from Survey Data
  8. Advance with Assist: Multiple Dashboard Actions with a Single Click
  9. Advance with Assist: Refreshing Tableau Online Data with Tableau Bridge
  10. Advance with Assist: Parameter Performance Optimization
  11. Advance with Assist: Using Custom Backgrounds with Polygon Shapefiles
  12. Advance with Assist: Changing Default Properties on Data
  13. Advance with Assist: Options for Calculating Percentages
  14. Advance with Assist: Removing Options from Filter List
  15. Advance with Assist: Extracting Year from De-identified Text String
  16. Advance with Assist: Marking the Latest Date on Trend Line
  17. Advance with Assist: What You Need to Know About Aliases
  18. Advance with Assist: Function Compatibility
  19. Advance with Assist: Mass Parameter Replacement
  20. Advance with Assist: Sorting with MONTH in Reverse
  21. Advance with Assist: Ungroup Column Headers That Have Concatenated
  22. Advance with Assist: Connectionless Failure Error in Tableau Server
  23. Advance with Assist: How to Exceed Tableau’s Column or Row Limit
  24. Advance with Assist: Adding Email Links to Your Dashboard
  25. Advance with Assist: Saving User-Selected Filters on Tableau Server
  26. Advance with Assist: Tableau and Named Ranges in Excel
  27. Advance with Assist: Editing Custom Fields in Tableau-Published Data Sources
  28. Advance with Assist: NOW and TODAY Functions in Tableau
  29. Advance with Assist: Sheet Swapping with Dummy Headers
  30. Advance with Assist: REST Error in Tableau and Snowflake Connection
  31. Advance with Assist: Mapping with One Data Row in Tableau 2019.2
  32. Advance with Assist: Multi-Number Formats for Single Calculations
  33. Advance with Assist: Removing Background Landmass on a Tableau Map
  34. Advance with Assist: Filtering Data Sources on Tableau Server
  35. Advance with Assist: Swapping Sheets in Tableau 2019.2
  36. Advance with Assist: Filling in Null Records Without Filtering
  37. Advance with Assist: Nested IF Calculations in Tableau
  38. Advance with Assist: Getting Show/Hide Buttons to Appear in Tableau Desktop
  39. Advance with Assist: Alteryx Output Error
  40. Advance with Assist: Missing Joins in Tableau 2020.2
  41. Advance with Assist: Tableau Server – Interactive MicroService Container Degraded
  42. Advance with Assist: A Shortcut for Duplicating Calculations
  43. Advance with Assist: Tableau Server License Renewal Refresh 
  44. Advance with Assist: Encrypt Tabcmd Credentials
  45. Advance with Assist: Pointing Tableau to a Named Range
  46. Advance with Assist: Tableau Server Migrations

More About the Author

Mitchell Scott

ServerCare Lead
Advance with Assist: Tableau Server Migrations Question: I need to migrate Tableau Server; what are my options? Should I be using something like Azure Site Recovery or AWS AMIs to ...
Advance with Assist: Encrypt Tabcmd Credentials Question: I need to script tabcmd commands but can’t leave passwords in plaintext inside scripts! How can I script tabcmd ...

See more from this author →

Subscribe to our newsletter

  • I understand that InterWorks will use the data provided for the purpose of communication and the administration my request. InterWorks will never disclose or sell any personal data except where required to do so by law. Finally, I understand that future communications related topics and events may be sent from InterWorks, but I can opt-out at any time.
  • This field is for validation purposes and should be left unchanged.

InterWorks uses cookies to allow us to better understand how the site is used. By continuing to use this site, you consent to this policy. Review Policy OK

×

Interworks GmbH
Ratinger Straße 9
40213 Düsseldorf
Germany
Geschäftsführer: Mel Stephenson

Kontaktaufnahme: markus@interworks.eu
Telefon: +49 (0)211 5408 5301

Amtsgericht Düsseldorf HRB 79752
UstldNr: DE 313 353 072