3-67
User Guide for CiscoWorks Common Services
78-16571-01
Chapter 3 Configuring the Server
Effects of Backup-Restore on Groups
Effects of Backup-Restore on Groups
Backup- Restore operations have an implication on the way Groups will be
displayed in the Common Services (CS) UI. The changes in Groups behavior is
discussed in relation with the Device and Credential Repository (DCR) mode
changes explained in the above section.
If you perform a backup on machine A and restore the backed up data, say Ab, on
the same machine, the system defined groups, and the user defined groups created
after the data backup will be removed.
Restoring data from a DCR Standalone
The following scenarios have to be considered:
•
Restore data from a Standalone machine A to another Standalone machine B:
The provider group name will change accordingly. That is, the provider group
CS @A will become CS@B.
•
Restore data from a Standalone machine A to a Master M:
The Master will switch to Standalone mode. The provider group name will be
updated accordingly. The Slave groups will be removed from the Master.
Only the groups pertaining to Common Services and the applications
installed in the Standalone machine will be visible. All dependent Slaves of
M will become Standalone.
•
Restore data from a Standalone machine A to a Slave S:
The Slave will switch to Standalone mode. The provider group name is
updated accordingly. The groups pertaining to other Slaves in the domain,
and the Master of S, will be removed from S. The groups UI will be enabled.
The subsequent sections are based on the scenarios discussed in the
“Effects of
Backup-Restore on DCR” section on page 3-63
.
Restoring data from S1 on S1
No impact on CS groups.
There may be applications installed on S1. Say you create 10 groups in the
Applications before you backup data from S1. After backup, say you create 10
more groups in the Applications. On restore, the 10 groups you created after
backup will not be present. This propagates to other Slaves in the domain also.