Regularly backing up Tableau Server is an important step in proper administration and maintenance of your server. You can use the tsm maintenance restore command to restore Tableau Server backups created using tabadmin backup and tsm maintenance backup. Database backups made in other ways, and virtual machine snapshots are not valid sources for restoring Tableau Server, so it is critical that you have an up-to-date backup. Show
You can only restore from a backup that has the same type of identity store as the running server. For example, a backup from a server using local authentication can be restored to a Tableau Server initialized with local authentication, but a backup from a server using Active Directory authentication cannot be restored to a server initialized with local authentication. Looking for Tableau Server on Linux? See Back Up Tableau Server Data(Link opens in a new window). Tableau Server data includes data extract files, as well as the Tableau PostgreSQL database, which contains workbook and user metadata, and configuration data. When you use TSM to create a backup, all of this data is saved in a single file with a .tsbak extension. If you are running a distributed installation of Tableau Server data from all the nodes is backed up. The frequency of your backups depends on your environment, including how much use your server gets and how much and frequently the content and users change. Any changes or updates that happen after your backup will be lost if there is a system failure and you need to restore Tableau Server. The more activity there is, the more often you need to back the server up. In addition to regular backups, you should always create a backup before upgrading to a new version of Tableau Server. To help protect against data loss, after you create the backup, you should store the .tsbak file on a computer that is not a part of your Tableau Server installation. Disk Space Usage for BackupThe free disk space required to create a backup varies depending on the amount of data in the Tableau Server repository and file store services, and their collocation with the tabadmincontroller service. During backups, the background tasks for cleaning up old extracts are temporarily paused. This means that, for the duration of the backup, extract refreshes will leave extra files in place, adding to disk space usage. If your backup takes a long time, or if your organization uses many extracts that are regularly updated, this can result in a significant amount of temporary disk space usage. These temporary files will be removed after the backup is complete. The following table lists the disk space requirements for backup based on whether the node hosts the repository, file store, controller, or some combination of them.
Optimizing Tableau Server BackupThere are several ways you can maximize backup efficiency. Your environment can impact how effective each of these is, so test with your data to see what works best. Optimizing with topology configurations:
The Administration Controller is usually on the initial node, unless you have had an initial node failure and moved the controller to another node. Optimizing with backup strategies: Backup is a resource intensive process. If possible, doing your backups during off peak hours is a generally a good strategy. But this however, depends on your requirements and how often Tableau Server data is updated and what your restore requirements. For a detailed explanation of backup and disaster recovery, see Tableau Server Disaster Recovery. Here are some backup strategies and adopt them to your requirements
Create a backup using the TSM command line interface (CLI)Use the tsm maintenance backup command to create a backup of the data managed by Tableau Server. This data includes data extract files and the Tableau PostgreSQL database, which contains workbook and user metadata. Before backing up Tableau Server, verify that permissions are configured correctly for the following scenarios:
To back up server configuration data, use the tsm settings command. When you use the tsm maintenance backup command, the current date is appended to the backup file: tsm maintenance backup -f <backup_file> -d For more information, see tsm maintenance backup. Create a pre-upgrade backupYou should always create a backup before upgrading Tableau Server. You can create a backup while Tableau Server is running and minimize the amount of time the server is unavailable during upgrade. The process for creating a pre-upgrade backup is the same as for creating regular backups, with one additional consideration for distributed installations. Note: Uninstall Tableau Server from any nodes that you are not including in your new installation to avoid conflicts between the older nodes and the new installation. Backups during upgradesDuring a Tableau Server upgrade, a temporary backup of the database is created to allow for migrations that occur as part of upgrades. This is done during the upgrade and in most cases has no noticeable impact to the upgrade process. In certain special cases there can be additional impacts:
Scheduling and Managing BackupsBeginning in 2020.4.0 you can use tsm commands to schedule a backup. You need to do this from the command line (there is no TSM UI to schedule backups). The tsm maintenance backup command allows you to create and update backup schedules. The tsm schedules commands give you the ability to view, delete, pause, resume, and update schedules. To schedule a backup:
To view a scheduled backup:
To update a scheduled backup:
To suspend or resume a backup schedule:
Script the backup processIf you back up often, you might want to create a script that performs the backup and related tasks for you. These tasks include:
This section discusses tsm commands you can use together to perform a backup and related tasks. Note: TSM is a batch file. To run tsm commands in another batch file, use the call command. For example "call tsm maintenance ziplogs". Doing this will return control to the batch file. You also need to authenticate to TSM before issuing any commands. For more information, see Authenticating with tsm CLI. For additional information about scripting TSM commands, see the Tableau Community Forums(Link opens in a new window). Remove log files and clear temporary foldersYou can clean old Tableau Server log file and temporary files to reduce the time it takes to create a backup, and to ensure the backup file is as small as possible. To clean log files older than a few days, run the following command: tsm maintenance cleanup Run the backupNote: When backing up Tableau Server on Windows to a network drive, the Machine account must have write access to the network share where the backup files are written (this is not normally the case and you are responsible for configuring this if you want to back the server up to a network share). To create the backup, use the tsm maintenance backup command: tsm maintenance backup --file <backup_file> --append-date Note the following about the command:
Copy the backup file to another computerAs a best practice, after the backup is created, copy the backup file to another location that is separate from Tableau Server. What are some proper ways to clean and control the build up of dust on or within a personal computer PC )? Select three?How to clean your computer, Step 1: Hardware. Wipe down your computer. ... . Clean Your keyboard. ... . Blow dust buildup out of computer vents, fans and accessories. ... . Run check disk tool. ... . Check surge protector. ... . Keep PC ventilated. ... . Back up your hard drives. ... . Get antivirus software to protect from malware.. What includes the practices and procedures that govern how an organization will respond to an incident in progress?The incident response policy serves as the cornerstone of an organization's incident response program. This policy should be written to guide efforts at a high level and provide the authority for incident response.
What sets out procedures and reporting guidelines for dealing with security incidents?The Federal Information Security Management Act (FISMA) requires Federal agencies to establish incident response capabilities. Each Federal civilian agency must designate a primary and secondary point of contact (POC) with US-CERT and report all incidents consistent with the agency's incident response policy.
What is it called when you have two sets of interlocking doors inside a small space where the first set of doors must close before the second set opens?A mantrap, air lock, sally port or access control vestibule is a physical security access control system comprising a small space with two sets of interlocking doors, such that the first set of doors must close before the second set opens.
|