Chapter 6 Upgrading Broadband Access Center for Cable
Migrating the RDU Database
When running this script, use this syntax:
./migrateDb.sh temp_dir
Where temp_dir identifies the temporary directory.
When performing this migration, you must allow for the available disk space required for temporary storage. The available disk space must be at least the same as the size of the old database files. However, for performance reasons, Cisco recommends that you locate this directory on a different disk from the database and the database log files.
Internally, the migration process from BACC 2.5.0.2 is a
•If migration is interrupted during the first part, from BACC 2.5.0.2 to BACC 2.6, migration restarts from where it left off, and the same migration log continues to be used.
•If migration is interrupted during the second part, from BACC 2.6 to 2.7, migration restarts from the beginning. The old migration log is renamed with a suffix with the timestamp and a new migration log is created.
If migration is interrupted during the first part, and a clean restart of migration from BACC 2.5.0.2 is required, you must:
Step 1 Delete all files from the temporary directory.
Step 2 Rerun the database migration script.
Step 3 Start the RDU to initialize the database.
Step 4 Run the verifyDb.sh script to verify database consistency (optional).
Step 5 Restart the RDU after migration is complete and the database verified.
Migrating from BACC 2.6
When migrating 2.6.x, no command line parameter is needed.
Use this syntax:
./migrateDb.sh
Migrating from BACC 2.6 generates a migration26to27.log file.
Interrupting the migration from BACC 2.6.x to BACC 2.7 restarts the migration from the beginning. The old migration log is renamed with a suffix with the timestamp and a new migration log is created.
Cisco Broadband Access Center for Cable Installation Guide 2.7
|
| ||
|
|