Cisco Cisco Broadband Access Center Telco Wireless 3.7
7-5
Cisco Broadband Access Center for Cable Administrator’s Guide
OL-2445-02
Chapter 7 Database Management
Backup and Recovery
The backupDb.sh command also reports progress to the screen and and logs its activity into history.log.
Note
When using the backupDb.sh command, you can use a –help option to obtain usage information. You
can also use another optional flag called -nosubdir to disable, if necessary, the automatic creation of the
subdirectory.
can also use another optional flag called -nosubdir to disable, if necessary, the automatic creation of the
subdirectory.
Database Recovery
Database recovery is the process of restoring the database to a consistent state. Since backup is
performed on a live RDU, the database can be changing while it is being copied. The database log files
however, ensure that the database can be recovered to a consistent state.
performed on a live RDU, the database can be changing while it is being copied. The database log files
however, ensure that the database can be recovered to a consistent state.
Recovery is performed on a snapshot of a database. In other words, this task does not involve touching
the database on the live RDU server. The recovery task can be performed either immediately following
a backup or prior to restoring the database to the RDU server.
the database on the live RDU server. The recovery task can be performed either immediately following
a backup or prior to restoring the database to the RDU server.
Note
Cisco recommends that you perform database recovery immediately after each backup. This way, the
backed up database can be more quickly restored in case of emergency.
backed up database can be more quickly restored in case of emergency.
The duration of database recovery depends on the number of database log files that had to be copied as
part of the backup, which in turn depends on the level of RDU activity at the time of the backup. The
more concurrent activity RDU experiences during the backup, the more transaction log files have to be
copied as part of the backup and the longer is the recovery. Generally, recovering a database takes from
10 to 60 seconds per transaction log file.
part of the backup, which in turn depends on the level of RDU activity at the time of the backup. The
more concurrent activity RDU experiences during the backup, the more transaction log files have to be
copied as part of the backup and the longer is the recovery. Generally, recovering a database takes from
10 to 60 seconds per transaction log file.
Performing Database Recovery
You use the recoverDb.sh command, located in the <BPR_HOME>/rdu/bin directory, to perform
recovery of the snapshot of a database.
recovery of the snapshot of a database.
When you use the recoverDb.sh command, you must provide the location of the backup. This is also the
directory in which the recovery will be performed.
directory in which the recovery will be performed.
Examples
Here is an example of using the recoverDb.sh command:
# recoverDb.sh /var/backup/rdu-backup-04272003-130345
In this example, the snapshot located in the /var/backup/rdu-backup-04272003-130345 directory will be
recovered to a consistent state. The progress of the recovery operation will appear on screen and the
activity will be recorded in the history.log file in the snapshot directory.
recovered to a consistent state. The progress of the recovery operation will appear on screen and the
activity will be recorded in the history.log file in the snapshot directory.
Note
When using the recoverDb.sh command, you can use a –help option to obtain usage information on the
command.
command.