Filter
Top Products
10-4
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 10 Database Management
Backup and Recovery
Handling Out of Disk Space Conditions
When the RDU server runs out of disk space, it generates an alert through the syslog facility and the
RDU log. The RDU server then tries to restart automatically. When attempting to restart, the RDU server
may again encounter the
out of disk space error and attempt to restart again.
The RDU server continues trying to restart until free disk space becomes available. Once you free up
some disk space on the disk that is operating near a limit, the next time the RDU restarts it will succeed.
If the size of your database grows beyond the capacity of the current disk partition, then you should move
the database to a new disk or partition. For information on how to do this, see Changing Database
Location, page 10-7.
Note It is a good practice to monitor disk space utilization to prevent failure. See Using the disk_monitor.sh
Tool, page 20-4, for additional information.
Backup and Recovery
The RDU server supports a highly efficient backup process that can be performed without stopping the
server or suspending any of its activities. Database backup and recovery involves these stages:
• Backup—Takes a snapshot of the RDU database from a live server.
• Recovery—Prepares the database snapshot for re-use.
• Restore—Copies the recovered database snapshot to the RDU server.
Automated tools are provided for each of these steps. You can use these tools in either interactive mode
or silent mode, but you must have root privileges to use the tools.
Note A non root user is provided with privilege to create directory only under the directories with non root
access.
Database Backup
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.