Cisco Cisco Broadband Access Center for Cable 5.0
7-3
Cisco Broadband Access Center for Cable Administrator’s Guide
OL-2445-02
Chapter 7 Database Management
Disk Space Requirements
Note
Database transaction logs are an integral part of the database. Manual deletion of transaction log files
may result in database corruption.
may result in database corruption.
Miscellaneous Database Files
The database directory contains additional files that are essential to database operation. These files, in
addition to the bpr.db file, are found in the <BPR_DATA>/rdu/db directory and are copied as part of the
database backup:
addition to the bpr.db file, are found in the <BPR_DATA>/rdu/db directory and are copied as part of the
database backup:
•
DB_VERSION—This log file identifies the physical and logical version of the database and is used
internally by the RDU.
internally by the RDU.
•
history.log—This file is used for logging activity about essential database management tasks, such
as automatic log file deletion, backup, recovery, and restore operations. In addition to providing
useful historical information for the administrator, this log file is essential to RDU database
operation.
as automatic log file deletion, backup, recovery, and restore operations. In addition to providing
useful historical information for the administrator, this log file is essential to RDU database
operation.
Disk Space Requirements
The size of a fully populated database is dependent on a number of factors. Key among them, is the
number of device objects managed by the RDU and the number of custom properties stored on each
object. The approximate estimates for disk space required on each partition are:
number of device objects managed by the RDU and the number of custom properties stored on each
object. The approximate estimates for disk space required on each partition are:
•
BPR_DATA – approximately 3 to 5 KB per device object
•
BPR_DBLOG – at least 500 MB
Caution
These numbers are only provided as a guideline and do not eliminate the need for normal system
monitoring.
monitoring.
You can use the disk_monitor.sh command to monitor available disk space and alert the administrator.
See the
See the
for additional information.
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.
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 running into a limit, the next time the RDU restarts it will succeed.
some disk space on the disk that is running into a limit, the next time the RDU restarts it will succeed.
If your database grows in size beyond the capacity of the current disk partition, then you should move
the database to a new disk/partition. To do this, simply perform steps outlined in the
the database to a new disk/partition. To do this, simply perform steps outlined in the
Note
It is a good practice, to monitor disk space utilization to prevent failure. See the
for additional information.