Senior Consultant    

2 min read

Backup and Recovery of Tableau Server using TSM - cont...

Please refer to part1 here.


2) Configuration and Topology data backup


In previous post, we have seen the repository backup and restore. But what about our topology information like number of processes, smtp configurations, etc. We must have these as well in our backup to fully recover server.  These are all included in the Configuration and Topology data backup. It defines how our Tableau Server is configured.

Below are the steps to perform Configuration and Topology data backup and restore.

To backup -- tsm settings export -f .json

To restore -- tsm settings import -f .json


S1) Verify the current status of system and let's take the existing Configuration and Topology data backup using tsm settings export -f A:\toplogyset.json as shown below.

S2) Adding one more process for Application server and Backgrounder. It requires a restart to bring the new topology to effect. Adding new process and restart can be done via TSM web UI. URL for TSM web UI is https://localhost:8850/ 

S3) To restore the initial settings, import the backup(A:\toplogyset.json) into server using tsm settings import -f A:\toplogyset.json and apply the pending changes using tsm pending-changes apply


S4) Login to TSM web UI to verify if the service topology has been restored. 


3) Manual backups

           TSM maintenance backup and export will not include information like customization, keystores, keytab files, etc. We have to take copy these files to a location regularly to have them backed up. Below are the list of files which need a manual backup.

  • Service Account 
  • Coordination Service deployment configuration
  • Customization settings
  • Access passwords to your postgres repository
  • Certificate files, keytab files, etc

This is all about backup and recovery of Tableau Server. It can be on same server or different server. Make sure you have these 3 backups always available with you before you start recovery.


Best Practices to follow.

  • Depends on size of your data, backup process can take time. So make sure you run these backup jobs during your off businsess hours. No other jobs can run in parallel to backup job. 
  • Once backups are successfully taken, make sure the files are copied to a different server. So that it can be resored even in case of a server's loss.
  • For repository backup, always use option -d which appends the date.

Hope it helps.

Never miss a story from us, get weekly updates in your inbox.