Backup is the process of
copying the database files into a backup directory. The files can then be
compressed and placed on tape or other archive.
RDU database backup is highly
efficient because it involves just copying files without interrupting server
activity. However, because it involves accessing the RDU database disk, backup
may adversely affect RDU performance. The opposite is also true. RDU activity
happening during backup will adversely affect backup performance. Therefore,
you should perform backups during off-peak hours.
Other than concurrent system
activity, backup performance also depends on the underlying disk and file
system performance. Essentially, backup will perform as fast as database files
can be copied from source to target.
Use the backupDb.sh tool, in
the BPR_HOME/rdu/bin directory, to perform database backups:
To use this tool, you must
provide the target directory where the backup files will be placed. This
directory should be on a disk or partition that has available disk space
equivalent to 120% of the current database file size.
As illustrated in the
following example, this tool automatically creates a timestamped subdirectory,
under the directory you specify, and places the backups there. You can also use
–nosubdir flag to
disable, if necessary, the automatic creation of the subdirectory.
To avoid database crash, the
Prime Cable Provisioning backup tool must be used if the backup is done while
the RDU is running. The database backup made by other file backup tools may not
be recoverable if the RDU modifies the database file during the backup.
The backupDb.sh command also
reports progress to the screen and logs its activity in history.log.
When using the backupDb.sh
tool, you can use a –help option to obtain usage information.
In this example,
the target location for database backup files.
# /backupDb.sh -nosubdir -throttle 500 /var/backup.
Database backup started
Back up to: /var/backup
Copying DB_VERSION. Size: 396 bytes.
DB_VERSION: 100% completed.
Copying bpr.db. Size: 434176 bytes.
bpr.db: 100% completed.
Copying log.0000000001. Size: 469268 bytes.
log.0000000001: 100% completed.
Copying history.log. Size: 574 bytes.
history.log: 100% completed.
Database backup completed
The timestamped subdirectory
format is rdu-backup-yyyyMMdd-HHmmss. In this example, the subdirectory would
be rdu-backup-20070316-031028, meaning that the directory contains a backup
that was started at 3:10:28 a.m. on March 16, 2007.
Once migration is complete, you can run the verifyDb.sh tool to
check the integrity of the database. Verification is an optional task. For more
information on verifyDB.sh, see
Using verifydb.sh Tool.