dbbackup — a script that backs up and restores the CommandCentral Storage database
dbbackup backupDir [-o [dbbackup_logfile]]
dbbackup backupDir -restore [restoreDir]
dbbackup backupDir -novalidate [-o [dbbackup_logfile]]
dbbackup backupDir -dbvalid [-o [dbbackup_logfile]]
dbbackup is a script used for backing up and restoring the CommandCentral databases. The script also performs a database validation of backed up databases.
(Required) backupDir is the directory where the CommandCentral database is backed up to, or restored from. backupDir should be an absolute path.
Restores the CommandCentral database from a previous database backup residing in backupDir.
(Optional) restoreDir is the directory to which the CommandCentral database is restored. If not included, dbbackup restores the database to the default data directory (/var/VRTSccs/database/). restoreDir should be an absolute path.
- -o dbbackup_logfile
Records dbbackup actions to a log file. Because validation is a standard part of the backup process, the log file includes validation information.
If dbbackup_logfile is unspecified, output is written to a file named dbbackup_log in the current directory.
If the -o option is not specified during backup , no log files are created.
Lets you skip the database validation in the database back up process.
Lets you perform database validation on any database that is backed up and saved in the backupDir directory. Using this option does not perform a database back up. If no log file is specified, the validation output is written to dbvalid_log in the current working directory.
dbbackup resides on Management Servers by default in: /opt/VRTSccs/VRTSccsts/bin
On Windows, you perform backups with the dbbackup.bat batch file, that resides by default in:
\Program Files\VERITAS\CommandCentral Storage\Support\tools
See Backing up the CommandCentral database
During restores, both the Solaris and the Windows scripts automatically stop and restart the database.
If a database back up process is already running when you run the dbbackup command, the system prompts you to try again later.
If the database validation process fails, a message prompts you to run the database back up again with the -o option specified for logging.
EXAMPLE 1: The following command backs up the CommandCentral database to the my_db_backups directory:
/opt/VRTSccs/VRTSccsts/bin/dbbackup /my_db_backups -o
Logging is turned on to write database backup and validation output messages to a log. Because a log directory is not specified, the dbbackup log is written to the file
dbbackup_log in the current directory.
EXAMPLE 2: The following command restores previously backed up CommandCentral database to the /var/VRTSccs/database/ directory:
/opt/VRTSccs/VRTSccsts/bin/dbbackup /my_db_backups -restore
Because a restore directory is not specified, dbbackup restores the database to the default data directory (/var/VRTSccs/database/).
EXAMPLE 3: The following command backs up the CommandCentral database to the my_db_backups directory but does not perform database validation:
/opt/VRTSccs/VRTSccsts/bin/dbbackup /my_db_backups -novalidate
Because the -o option is not specified, no
dbvalid_log files are created.
EXAMPLE 4: The following command runs a validation of the previously backed up CommandCentral database that is saved in the my_db_backups directory:
/opt/VRTSccs/VRTSccsts/bin/dbbackup /my_db_backups -dbvalid -o
Because no log file directory is specified, dbbackup writes the
dbvalid_log file to the current working directory.