Backing up the Presentation Server database
To ensure the availability and integrity of your data, you must periodically back up the database files for the 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:
Backup frequency
The state of the recovery 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.
By default, the TrueSight Presentation Server automatically performs a database backup every 24 hours.
Manually creating a backup of the database
Note
Ensure that the database service is running before you create a manual backup of the database.
Run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:
tssh database startbackupA backup of the database is created in the <Presentation Server installation directory>\truesightpserver\data\dbbackup folder.
Changing the automatic database backup settings
The following table lists the default automatic database backup settings. To change a setting, run the appropriate command from the <Presentation Server installation directory>\truesightpserver\bin folder.
| Parameter | Default setting | Command to change setting |
|---|---|---|
| Backup time | 3.30 AM (TrueSight Presentation Server timezone) |
Example: |
| Backup frequency | Every 24 hours |
Example: |
| Number of backups retained | The latest three backups |
Example: |
Restoring a backup of the database
Run the following command to restore the backup of the database:
(On Windows) :
tssh database import %TRUESIGHTPSERVER_HOME%\data\dbbackup\db_<date_timestamp>\base.tar.gz(On Linux) :
tssh database import $TRUESIGHTPSERVER_HOME/truesightpserver/data/dbbackup/db_<date_timestamp>/base.tar.gz
Important
In case TrueSight Presentation Server is configured with a high-availability (HA) setup, ensure that before running the database import command, the server running in standby mode is stopped.
Otherwise, while starting the server there is a chance of database snapshot from the secondary server overwriting the database on primary server.
Note
- On Linux computers, add
&at the end of thetssh server startcommand 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.
Related topics
Setting up and managing the App Visibility components and databases
Comments
Log in or register to comment.