Archiving, restoring jobs, and creating backup files
You can archive and then restore information about BMC Database Automation jobs for a date range that you specify. You can create backup files of all state, configuration and log information. The backup script is stored in this location on the Manager:
/app/clarity/manager_scripts/bin/clarity_backup.pl
The required format is as follows:
clarity_backup.pl [-b begin_date -e end_date | -r file] [-h] [-d file] [-l file] [-s] [-w] [-v]
The options for this command provide the following:
Command option | Description |
|---|---|
-h | Usage |
-c | Create backup |
-a | Archive only (does not include configuration files); requires -b and -e |
-b | Beginning date in format YYYY-MM-DD |
-e | Ending date in format YYYY-MM-DD |
-r | Restore files from specified .zip file |
-d | Destination .zip file name |
-l | Log to the specified file. |
-s | Do not stop/start services, leaving the Manager and database running. Useful for archiving, but not recommended for full backups. |
-w | Do not include provisioning log files. |
-v | Verbose |
For example, to archive all logs and jobs between April 1 and April 7 2010:
export LD_LIBRARY_PATH=/app/clarity/lib
clarity_backup.pl -a -b 2010-04-01 -e 2010-04-20 -s -v
To restore the archive in the example:
export LD_LIBRARY_PATH=/app/clarity/lib
clarity_backup.pl -r clarity_backup-2010-04-19-31943.zip -v
To backup all state, configuration and log information:
export LD_LIBRARY_PATH=/app/clarity/lib
clarity_backup.pl -c