Cisco Cisco Broadband Access Center Telco Wireless 3.8
7-2
Cisco Broadband Access Center for Cable Administrator’s Guide
OL-2445-02
Chapter 7 Database Management
Database Files
Database files are vital to the operation of the RDU and you should take extra precaution measures for
safeguarding them against accidental removal or other manual manipulation. Follow standard system
administration practices for safeguarding these important files. For example, these files should always
have permissions that allow only root user access. Additionally, it is a good practice to never login to
your production system as a root user, but rather log in as a less privileged user and use the sudo
command to execute tasks requiring root privileges.
safeguarding them against accidental removal or other manual manipulation. Follow standard system
administration practices for safeguarding these important files. For example, these files should always
have permissions that allow only root user access. Additionally, it is a good practice to never login to
your production system as a root user, but rather log in as a less privileged user and use the sudo
command to execute tasks requiring root privileges.
Note
Use the backup, restore, and recovery tools to perform corresponding tasks on the database. Previous
Broadband Provisioning Registrar (BPR) releases allowed performing some of these tasks directly
without utilizing specific tools. Do not attempt to perform these tasks without utilizing the tools. See the
Broadband Provisioning Registrar (BPR) releases allowed performing some of these tasks directly
without utilizing specific tools. Do not attempt to perform these tasks without utilizing the tools. See the
for additional information on these tools.
Database File
The RDU server stores its database in a file called bpr.db, which is found in the database directory. This
directory is located in the <BPR_HOME>/rdu/db directory and is configured by specifying the
BPR_DATA parameter during a component installation. See the
directory is located in the <BPR_HOME>/rdu/db directory and is configured by specifying the
BPR_DATA parameter during a component installation. See the
for additional information on moving the database.
Note
The database file is normally accessed in a random fashion. You should therefore, select a disk with the
fastest seek time, and rotational access latency, to obtain the best database performance.
fastest seek time, and rotational access latency, to obtain the best database performance.
Database Transaction Log Files
The RDU server stores database transaction logs in 10 MB files that are stored in the database log
directory. This directory is configured during installation by specifying the BPR_DBLOG parameter.
The log directory is located in the <BPR_DBLOG>/rdu/dblog directory. See the
directory. This directory is configured during installation by specifying the BPR_DBLOG parameter.
The log directory is located in the <BPR_DBLOG>/rdu/dblog directory. See the
directory.
Database log files are named in numeric sequence, starting at log.00000001, then log.00000002, and so
on.
on.
Note
The disk on which transaction logs are stored is usually accessed in a sequential manner, with data being
appended to the log files. Select a disk that can efficiently handle this access pattern to achieve the best
database performance.
appended to the log files. Select a disk that can efficiently handle this access pattern to achieve the best
database performance.
Automatic Log Management
Database transaction logs files are used to store transaction data until that data is completely written into
the database. After that, the transaction log data becomes redundant and, because the RDU server
database manages transaction log files automatically, the files are then automatically removed from the
system. Under normal circumstances there should be only a few log files in the database transaction log
directory. Over time, you will notice that older transaction logs disappear and newer ones are created.
the database. After that, the transaction log data becomes redundant and, because the RDU server
database manages transaction log files automatically, the files are then automatically removed from the
system. Under normal circumstances there should be only a few log files in the database transaction log
directory. Over time, you will notice that older transaction logs disappear and newer ones are created.