|
|
This appendix describes the Cisco Access Registrar shadow backup facility, which ensures a consistent snapshot of Cisco Access Registrar's database for backup purposes.
Because the Cisco Access Registrar's database (called MCD) does a variety of memory caching, and may be active at any time, you cannot simply rely on doing system backups to protect the data in the database. At the time you run a system backup, there may be Cisco Access Registrar operations in progress that cause the data copied to the system backup tape to be inconsistent and unusable as a replacement database.
The only configuration for this facility is through a single entry in the system Registry.
For a UNIX system, /opt/AICar1/conf/aic.conf is the registry path to this item.
This entry is a string that represents the time-of-day at which the shadow backup is scheduled to occur (in 24 hour HH:MM format). The default is 23:45.
When you remove this entry or set it to an illegal value (for example, anything that does not begin with a digit), backups are suppressed. The server is otherwise unaffected.
In addition to being available at a scheduled time of day, you can also force a shadow backup by using the mcdshadow utility located in the /opt/AICar1/bin directory for a UNIX system. There are no command-line arguments.
This may take a few minutes to complete as a full copy of the database is created.
When it is necessary to use the shadow backup to recover data, either because the regular working database has been corrupted by a system crash, or because the disk on which it resides has become corrupted, perform the following:
Step 1 Stop all Cisco Access Registrar servers.
Step 2 Make sure three files (mcddb.d01, mcddb.d02, and mcddb.d03) exist in the /opt/AICar1/data/db.bak directory.
Step 3 Copy the files into the /opt/AICar1/data/db directory. Do not move them as they may be needed again.
Step 4 Change directory to the /opt/AICar1/data/db directory.
Step 5 Rebuild the key files by typing the command:
/opt/AICar1/ibin/keybuild mcddb
This can take several minutes.
Step 6 As a safety check, run /opt/AICar1/bin/dbcheck mcddb (UNIX) to verify the integrity of the database. Note, you must be user root to run dbcheck.
No errors should be detected.
The mcdshadow command uses the files listed in Table D-1.
| File | Description |
|---|---|
Template file that describes the low-level data schema for the Raima run-time library. | |
Key files that contain the data that is redundant with the data files. Cisco Access Registrar does not back up these files because they can be completely rebuilt with the keybuild command. | |
Data files that contain the backup. | |
Text file from which Cisco Access Registrar configures the initial at-install-time database. | |
Text file that contains a version number denoting the level of the schema contained in the dbd file. Note, Cisco Access Registrar w ill not attempt to open the database unless the number in this file matches a constant that is hard-coded in the libraries. If the result of the mcdshadow command (which it just uses copies of the data files) is divorced from its original mcdschema.txt, you will not be able to run Cisco Access Registrar. | |
Working files used by the Raima run-time library to ensure transactional integrity. |
Posted: Thu Aug 19 08:16:11 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.