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

50
VCEM section
During this section, the restored VCEM database is resynchronized with the state of the VC
Domains managed by VCEM. During the first phase, the mxsync tool scans the VC Domains
managed by VCEM. If changes occurred after backup that could cause the VCEM
product resynchronization to fail, the mxsync tool recommends making changes to the
restored VCEM database to resolve the identified issues.
For the sample run, the changes recommended by mxsync during phase 1 of section 2 are
summarized in Table 14.
Table 14. Summary of mxsync VCEM phase 1 actions
Post-backup Activity
Pre-mxsync State
VCEM Section Phase 1
mxsync Recommendation/Action
VCEM Section Phase 1
Deactivate logical
server LS1_VC_Test.
Deactivate
infrastructure
orchestration service
S4_VC_Test.
The profile is assigned to a blade in
the restored VCEM database, but
the profile no longer exists in the
underlying VC Domain
configuration.
Changed the state of the profile to
unassigned in the VCEM database.
Activate infrastructure
orchestration service
S1_VC_Test.
The profile is unassigned in the
restored VCEM database, but the
profile is assigned to a blade in one
of the underlying VC Domain
configurations.
Remove profile from the VCEM
database. The profile definition will
be recreated during phase 2.
Create logical server
LS2_VC_Test.
Create logical server
LS4_VC_Test.
Create logical server
LS5_VC_Test.
Create infrastructure
orchestration service
S3_VC_Test.
The profile does not exist in the
restored VCEM database.
Note: If the profile was assigned to a
blade when the failure occurred,
the profile definition will exist in one
of the underlying VC Domain
configurations. However, if the
profile was unassigned when the
failure occurred, the profile
definition will be lost and need to
be recreated.
The profile definition will be added
to the VCEM database during
phase 2.
Note: One or more addresses
assigned to the LS2_VC_Test profile
are still assigned to the LS3_VC_Test
profile in the restored VCEM
database. To resolve the duplicate
reference, the LS3_VC_Test profile
will be removed from the restored
VCEM database.
Delete logical server
LS3_VC_Test
Delete infrastructure
orchestration service
S2_VC_Test.
The profile is assigned to a blade in
the restored VCEM database, but
the profile no longer exists in the
underlying VC Domain
configuration.
Delete the LS3_VC_TEST and
S2_VC_TEST profiles from the
restored VCEM database.
Note: Unless resources have been
reallocated to another profile, it is
not possible to automatically
determine whether the profile was
unassigned or deleted post-
backup. To avoid the loss of data,
the VCEM profile is placed in an
unassigned state.
Note: The delete recommendations
for LS3_VC_TEST and S2_VC_TEST
were triggered because the
addresses assigned to the profiles
have already been reallocated to
new profiles in an underlying VC
Domain.