Backing up and Restoring HP Insight Management 7.0 Central Management Server (Windows)

Appendix E: VCEM resynchronization actions

There are some VC activities that, if performed post-backup, may require manual steps in

order to synchronize the state of the VC Domain with the restored VCEM database. The

manual recovery steps required to resynchronize VCEM to address the following operations

are documented in this appendix:

• Remove a VC Domain from a VC Domain Group

• Add a VC Domain to a VC Domain Group

• Add or remove VC modules

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 or removed from a VC Domain

Group. The same recommendation applies for adding/removing

VC modules or removing and recreating a VC Domain Group.

VC domain removed after backup

If a VC Domain was removed from a VC Domain Group (VCDG), after the VCEM database

is restored from backup, the VC Domain is still a member of the VCDG in the restored

VCEM database. You need to 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

the execution of mxsync.

1. During the analysis step of phase 1 in the VCEM 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 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 is marked

as EXTERNAL in the restored VCEM database. Any profiles in the restored VCEM

database using these addresses are deleted. These steps are necessary to ensure that

addresses assigned to the removed VC Domain and not re-used 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 Integrated

Consoles  Virtual Connect Enterprise Manager (VCEM)… from the Tools menu in Systems

Insight Manager. Select the VC Domain tab to view the status. If the VC Domain was

removed after backup, the status Missing External Manager Lock status is displayed.