3-63
User Guide for CiscoWorks Common Services
78-16571-01
Chapter 3 Configuring the Server
Effects of Backup-Restore on DCR
Effects of Backup-Restore on DCR
Data changes are a normal part of any restore from a backup. However, because
Device and Credential Repository (DCR) is a distributed system with varying
modes, it is also possible for any restored DCR to:
•
Change modes.
For example, a Standalone DCR can be set after a backup to act as a Slave.
When the restore is performed, it will be reset to Standalone mode. It depends
on source machine’s DCR mode where backup was taken, and on the target
machine’s DCR mode on which the data was restored.
•
Change master/slave relationships.
For example, a DCR Slave may be using Master A at the time a backup is
taken. Later, the domain may be changed to use Master B, and the Slave reset
to use Master B. When the restore is performed, the Slave will attempt to use
Master A.
For detailed information on DCR, see
Chapter 4, “Managing Device and
Credentials”
.
The following scenarios helps you understand the implications of Restore
operations on DCR.
Restoring data from a DCR Standalone
If you restore the data backed up from a machine in Standalone mode, on any
machine whose working mode is either Standalone, Master, or Slave, the end
mode will be Standalone.
Let X be a machine in standalone mode.
If you restore the data backed up from X, say Xb, on another Standalone machine
Y, or a Slave S, or a Master M, the end mode of Y, S, and M will be Standalone.
Also, any slave of M will switch to Standalone mode.
Further scenarios can be better explained based on the following DCR set up.
Let us assume there are two DCR domains.
•
For Domain 1, you have M1 as Master, and S1, and S2 as Slaves.
•
For Domain 2, you have M2 as Master, and S3, and S4 as Slaves.
