Cisco CISCOWORKS COMMON SERVICES 3.0 User Manual page 110

Chapter 3 Configuring the Server
Effects of Backup-Restore on DCR
Restoring data from S1 on S1
Suppose you take a backup from S1. After sometime, you restore the backed up
data, say S1b, on S1. S1 will look for its Master M1, and the Master-Slave relation
between S1 and M1 will be intact, since M1 is available.
However, note that the restore on S1 will practically be of no effect since S1 and
M1 will synchronize after the restore on S1. The changes that have taken place
after the backup was taken from S1 will be reflected in S1, even if S1b is restored
on S1.
In the above example, if the restore on S1 is performed when Master M1 is down,
or has crashed, the end mode of S1 will be Standalone. This is because S1 will try
to contact M1, and will fail because M1 is down.
Restoring Data From S1 to M1
Suppose you take a backup from S1 and restore the backed up data, say S1b, on
M1. M1 will switch to Standalone mode because, after backup, it will not be able
to find a Master. S1 will also switch to Standalone mode.
At the time of backup, if there were 1000 devices in M1, the Slave S1 would also
have 1000 devices. Say more devices are added to M1 after the Backup. S1 will
have the up-to-date device list. But after restore on M1, M1 will have only 1000
devices. In other words, the data on S1 will be more recent than that on M1.
Restoring Data from S1 on M2
Suppose you take a backup from S1 and restore the backed up data, say S1b, on
M2, which is the master in the DCR Domain 2 in our example.
After the restore, the end mode of M2 will be Slave. That is, M2 will become a
slave of M1. Also, S3, and S4, which were slaves of M2, will switch to Standalone
mode.
Restoring Data From M1 on M1
Suppose you take a back up from M1. After the backup you would be performing
several operations that would bring about changes in the Master and the
corresponding Slaves; M1, S1, and S2 in our example.
User Guide for CiscoWorks Common Services
3-64
78-16571-01