Backing up Tableau Server ensures recovery from failures or migrations. A full backup includes multiple data types—let’s dissect this comprehensively:
Backup Components:
Repository Data: PostgreSQL database with metadata (users, permissions, workbooks). Backed up via tsm maintenance backup -f .tsbak.
Configuration Data: Server settings (e.g., ports, authentication) also in the .tsbak file.
Server Secrets: Encryption keys, internal tokens, Repository passwords—critical for restoring functionality.
Extracts: .hyper files in File Store (optional, separate backup).
Option A (Server secrets and Repository passwords): Correct.
Details: Includes encryption keys (for extracts), internal tokens (process communication), and Repository credentials. Backed up separately or stored securely (e.g., tsm security export-keys).
Why Critical: Without these, restored data may be inaccessible or services may fail.
Option C (Configuration data): Correct.
Details: Ports, authentication settings, process topology—part of the .tsbak file.
Why Critical: Restores server behavior and connectivity post-recovery.
Option D (Repository data): Correct.
Details: Core metadata database—also in .tsbak.
Why Critical: Without it, all content and user data is lost.
Option B (Topology data): Incorrect.
Details: Topology (process distribution) is part of configuration data in the .tsbak, not a separate entity. It’s not distinctly backed up as “topology data.”
Why This Matters: A complete backup (secrets, config, repository) ensures full restoration—missing any piece risks an unusable server.
[Reference: Tableau Server Documentation - "Back Up Tableau Server Data" (https://help.tableau.com/current/server/en-us/backup_restore.htm)., , ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit