![]() ![]() Default value is 86400 (1440 minutes).ĭays on which to run the schedule. Number of seconds to wait for the command to finish. You can change the number of threads used by setting the _count configuration key.Īttempt to create a backup even when there is a low disk space warning. Two threads are used by default, when this option is specified. ![]() When this option is specified, a backup is created using multiple threads. Use this prompt if automating backups (for example, with scripts).ĭo not verify the integrity of the database backup.īy default, a single thread is used when creating a Tableau Server backup. Include the specified description of the backup file.īack up without prompting, even if the File Store is not on the same node as the Administration Controller (usually the initial node). For more information about scheduling backups, see Scheduling and Managing Backups. If you also use the -d option your file name will include the date twice. ![]() Note: Backups created using a schedule automatically include a date/time at the beginning of the backup file name. Tsm maintenance backup -file Optionsįor more information about backing up the repository data, see Back up Tableau Server Data for more information.Īppend the current date to the end of the backup file name. ![]() Note: Even when you change the backup location, the backup process uses a temporary location in the data directory to assemble the backup file. tsbakįor more information about where backup files are written, and how to change that location, see tsm File Paths. By default:Ĭ:\ProgramData\Tableau\Tableau Server\data\tabsvc\files\backups\. The backup file is assembled in a temporary location in the data directory and then written to the directory defined in the TSM basefilepath.backuprestore variable. The Administration Controller is usually on the initial node, unless you have had an initial node failure and moved the controller to another node. Co-locating the repository (pgsql) with the Administration Controller node can also help to reduce back up time, but the time savings is less significant than that of the File Store.This is especially true if your organization uses many extracts. Co-locating File Store on the same node as the Administration Controller can reduce the length of time it takes to back up Tableau Server by reducing or eliminating the need to transfer data between nodes during the backup process.See Backup and Restore with External File Store. Note: Do not use this command on Tableau Server installations with External File Store. See Perform a Full Backup and Restore of Tableau Server. This data does not include configuration data. This data includes the Tableau PostgreSQL database (the repository) which contains workbook and user metadata, and extract (.tde or. tsm maintenance snapshot-backup restoreĬreates a backup of the data managed by Tableau Server.tsm maintenance snapshot-backup prepare.tsm maintenance snapshot-backup complete.tsm maintenance snapshot-backup (external file store).tsm maintenance preflight-check permissions.tsm maintenance metadata-services get-status.tsm maintenance metadata-services enable.tsm maintenance metadata-services disable.The tomcat.pid file also resides in /temp, but it would be excluded from the purge, since only. The temp files filling up the directory are from user file uploads. This should be safe, no? I read that it is only truly safe to purge /temp when the server is shutdown, but I don't see why old temp files should be needed. I wrote a scheduled task that runs every two days and deletes all. Our server has a problem with the tomcat/temp dir filling up and not clearing itself. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |