To ensure the availability and integrity of your data, you must periodically back up the database files for the BMC TrueSight Presentation Server. BMC recommends that you use a storage replication solution to back up the database and configuration files at regular intervals.
This topic contains the following information:
The state of the recovery BMC TrueSight Presentation Server depends on how recently you backed up your files. According to your organization's IT policies, you can decide whether to have daily, weekly, or monthly backups.
Run all of the
tssh commands in this topic from the following directory if it is not in your PATH:
By default, the Presentation Server automatically performs a database backup every 24 hour. You can change this time interval by modifying the value of the dbBackupSchedulePeriod property. Whenever you change a backup property, changes to not take effect until you restart the Presentation Server.
tssh properties set dbBackupSchedulePeriod <hours interval>
The database backup files are stored in the following location:
By default, the Presentation Server stores the last three backup files of the database. You can change the number of stored backups by changing the value of the numOfBackups property.
tssh properties set numOfBackups <number of backups>
tssh properties set numOfBackups 7
BMC recommends that you initiate a backup of the files after making any configuration changes to the server. You can manually initiate a database backup by running the following command:
tssh database startbackup
To ensure that the files are synchronized, BMC recommends that you back up all of the files at the same time.
Stop the Presentation Server by running the following command:
tssh server stop
Restart the Presentation Server by running the following command:
tssh server start
On Linux computers, add
& at the end of the
tssh server start command so that the process runs in the background and you can continue to use the shell.
When you restore the database, some VM instances or devices are marked for deletion. For more information, see Knowledge Article KA426529 (Support logon ID required).