Alternative Database Backup?

[lwilson]

In our environment, we use Tivoli Storage Manager to back up our servers, including the Traverse servers (running on Linux machines). We have noticed lately that the backup jobs on the Traverse servers take far longer than they should because the mysql databases are in use during the backup.

We could remove the databases from the backup, but then we would have no backup of our system data. Is there some alternative method we can use to back the databases up to a file that can be easily restored into Traverse?

[rajib]

Hi Luke,

Are you using the database management tools that are provided with Traverse to perform the scheduled backup of these servers? Assuming you have added the contents of etc/emerald.crontab into root's crontab, a snapshot of the BVE and DGE databases should be created under database/backup directory every night. You can configure Tivoli Storage Manager to exclude database/mysql directory, which contains the "live" databases and backup the contents of the database/backup direcory instead.

The steps to restore BVE/DGE database from one of the nightly snapshots is outlined in section 16 (Maintenance and Disaster Recovery) section of the User Guide (http://zyrion.com/support/docs/).

[lwilson]

Thank you; that is exactly the information we needed. Those entries weren't automatically entered, so we didn't have the backups activated until you just told me how. With this running, we should get Traverse to work harmoniously with our Tivoli backup tools. I knew this capability would be in Traverse somewhere; I just didn't know where to look.