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

Technical white paper | HP Insight Management 7.3
Virtual Connect Enterprise Management 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 the backup that
might 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 the Virtual Connect Enterprise
Management section are summarized in Table 15.
Table 15. 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 infrastructure
orchestration services TC1
and expired TC7.
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.
Create infrastructure
orchestration services TC4,
TC5, and TC8.
Infrastructure orchestration
service TC6 was approved and
created.
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 will
need to be re-created.
The profile definitions will be
added to the VCEM database
during phase 2.
Note:
If any addresses assigned to a
new profile are still assigned to a
profile that was deleted post-
backup, the original profile will
be removed from the restored
VCEM database.
Delete infrastructure
orchestration services TC2
and TC3.
The profile is assigned to a blade
in the restored VCEM database,
but the profile no longer exists in
the underlying VC Domain
configuration.
Unassign the 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:
In both cases, addresses were not
reused in new profiles; therefore,
the profiles were unassigned, not
deleted, from VCEM.
43