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

40
There are two phases in this section. During the first phase, the mxsync tool analyzes the
WWN and MAC addresses assigned to profiles in the VC domains managed by VCEM to
identify addresses that were allocated or reassigned after backup.
An address could have been allocated if, for example, as a post-backup activity, a VC-
based logical server or infrastructure orchestration service was created. To prevent a post-
backup allocated address from incorrectly being reassigned to a second server during the
execution step of this phase, the mxsync tool marks these addresses as External in the VCEM
database.
An address could have been reassigned if a VC-based logical server was deleted, the
address freed, and then reassigned to a new logical server. To eliminate the conflict
caused by reassigning an address to a different VC profile during the execution step of this
phase, the mxsync tool deletes the definition of the VCEM profile that contains the
reassigned address.
If as a post-backup activity a VC Domain was added to or removed from a VC Domain
Group, the VC Domain is no longer accessible to VCEM after the VCEM database is
restored from backup. During phase 1, you are given the opportunity to provide the
credentials for the added or removed 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. If no VC Domains were added or removed after backup, you respond ”n” to the
prompt to provide credentials.
During the second phase, the mxsync tool issues requests to VCEM to resynchronize each
VC domain managed by VCEM.
Note:
During the analysis step of phase 2, mxsync displays an ISSUE for
each VC Domain managed by VCEM stating that the VC Domain
MAY need to be synchronized with VCEM. This is only a potential
issue. The test to check if the VC Domain is out of sync will
temporarily place the VC Domain in maintenance mode and
therefore can only be performed during the execution step.
If, as a post-backup activity a VC Domain was added to or removed from a VC Domain
Group, you need to manually re-issue the Add to VC Domain or Remove from VC Domain
operation to successfully complete phase 2. See Appendix E: VCEM resynchronization
actions for additional details.
mxsync Logical servers and associated SAN-based storage synchronization section
During this section, the restored HP Matrix Operating Environment and HP Storage
Provisioning Manager databases are updated.
There are three phases in this section.
During the first phase, the mxsync tool updates the presentation state of the storage
volumes in the restored HP Storage Provisioning Manager (SPM) database to reflect the
actual state of the storage volumes in the storage array. The tool starts the HP Extensible
Storage & Server Adapter, the HP SPM Storage Module J2EE Service, and the HP SPM Storage
Module Service Windows services, which need to be running prior to starting the HP Storage
Provisioning Manager Service Windows service. The mxsync tool instructs you how to place
the HP Storage Provisioning Manager Service Windows service in “InternalRecovery” mode by
editing the file <SPM>\state\ApplicationConfig.xml to change the <RecoveryMode>
property to InternalRecovery. It then starts the HP Storage Provisioning Manager Service
Windows service. At this time, you are instructed to check the SPM browser-based interface
at https://<servername>:8000 to determine when the Storage Provisioning Manager