Backing up the Backup Exec System Recovery Manager server and database
|Article:HOWTO13583|||||Created: 2008-01-05|||||Updated: 2013-10-17|||||Article URL http://www.symantec.com/docs/HOWTO13583|
Because the Backup Exec System Recovery Manager server also includes a database, you should back up the server on a regular basis. This requires you to stop the Backup Exec System Recovery Manager Web Services before backing up so you do not lose or corrupt data. To automate such a backup process, you can use Backup Exec System Recovery Manager to create a "cold" recovery point.
To backup the Backup Exec System Recovery Manager server and database
The backup job needs to run two command files: One command file to stop the Backup Exec System Recovery Manager Web Services before the snapshot is taken of the computer, and the other command file to restart the Web Services immediately after the snapshot.
Backup Exec System Recovery Manager ships with two pre-defined command files (StopServices.bat and StartServices.bat) that you can use during the backup of the server and database. The two command files are located at the following path on the Backup Exec System Recovery Manager product CD:
Make sure that the backup job will run at a time when backup jobs for other managed computers are not running. For example, if most of your backup jobs are scheduled to run at 2:00 A.M., the backup job for the Backup Exec System Recovery Manager server should run earlier than 2:00 A.M. (or later if you prefer).
Make sure that the Backup Exec System Recovery Manager server computer is not assigned to any Groups that you may have defined in the console. This ensures that backup jobs, intended for other computers, do not get assigned to the server.
Article URL http://www.symantec.com/docs/HOWTO13583