Backing up and restoring HP Insight Management 7.3 Central Management Server (Windows)

Technical white paper | HP Insight Management 7.3
Appendix E: VCEM resynchronization actions
Some VC activities, if performed after the backup, may require manual steps in order to synchronize the state of the VC
Domain with the restored VCEM database. This appendix documents the manual recovery steps required to resynchronize
VCEM to address the following:
Remove a VC Domain from a VC Domain Group
Add a VC Domain to a VC Domain Group
Add or remove VC modules
Update VC firmware
Disable the enclosure
Unable to communicate with the enclosure
Important:
In most environments, operations such as adding or removing a VC Domain from a VC Domain Group are expected to occur
infrequently. To avoid the manual steps required to perform this resynchronization, HP strongly recommends backing up
the CMS whenever a VC Domain is added to or removed from a VC Domain Group. The same recommendation applies to
adding and removing VC modules, or removing and re-creating a VC Domain Group.
VC Domain removed after backup
If a VC Domain was removed from a VC Domain Group (VCDG) after backup, the VC Domain is still a member of the VCDG in
the restored VCEM database. You must manually reissue the request to remove the VC Domain from the VCDG.
To remove the VC Domain from the restored database, perform the following steps during execution of mxsync:
1. During the analysis step of phase 1 in the Virtual Connect Enterprise Management section, mxsync displays a
message stating that the VC Domain is inaccessible. You are given the opportunity to provide the credentials for the VC
Domain. This allows mxsync to access the VC Domain to identify any WWN or MAC addresses that were assigned to
the VC Domain after the backup. This can happen if, for example, as a post-backup activity, a VC profile was assigned to
a blade in the VC Domain before the domain was removed from the VCDG.
During the execution step of phase 1, the identified WWN and MAC addresses are marked as EXTERNAL in the restored
VCEM database. Any profiles in the restored VCEM database that are using these addresses are deleted. These steps
are necessary to ensure that addresses assigned to the removed VC Domain and not reused by VCEM.
2. During the second phase, mxsync issues requests to VCEM to resynchronize each VC Domain managed by VCEM. Since
the removed VC Domain is still a member of the VCDG in the restored database, the resynchronization request is
issued. However, since this VC Domain is no longer managed by this VCEM, the request fails.
You can view the details of VCEM resynchronization tasks by selecting
Tools
Integrated Consoles
Virtual Connect
Enterprise Manager (VCEM)
in Systems Insight Manager. Click the
VC Domains
tab to view the status. If the VC Domain
was removed after the backup, the status
Missing External Manager Lock
is displayed.
76