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

Technical white paper | HP Insight Management 7.3
Type Names Pre-backup state Post-backup state
VMM HP IO Service Name: TC11
Logical server name: TC11esx-net01_ls
HP IO service is
created and
activated.
VMM HP IO Service Name: TC12
Logical server name:TC12hv-net01_ls
HP IO service is
created and
deactivated.
RM Recovery Group: RG1 LS-based recovery
group is created with
TC9esx-net01_ls.
Recovery group is
modified to add
TC11esx-net01_ls,
and export file is
created.
RM Recovery Group: RG2 IO-based recovery
group is created with
TC10.
TC10 is deleted, and
RG2 is removed.
The mxsync tool is divided into five sections that are executed in the following order:
1.
Systems Insight Manager
2.
Virtual Connect Enterprise Manager
(VCEM)
3.
Logical server and associated SAN-based storage
(LSM)
4.
HP Matrix infrastructure orchestration
(HP IO)
5.
HP Matrix recovery management
(RM)
Each section is responsible for identifying inconsistencies between the representation of a resource in its restored database
and that of the underlying updated layer.
Before starting the synchronization process, the mxsync tool checks the status of the HP Insight Management services and
recommends actions for stopping and starting services. If you respond y to the request to perform the recommended
changes, the required services will be started and all other services will be stopped.
Systems Insight Manager section
During this section, the restored Systems Insight Manager database is updated to reflect system changes that have
occurred after the backup. During execution, you are asked to log in to Systems Insight Manager and issue tasks to discover
Onboard Administrators, hypervisor host operating systems (VMware ESX servers or Microsoft Hyper-V servers), and
operating systems deployed on blades, VM guests, and standalone servers. The mxsync tool pauses while you complete
discovery. After discovery is complete, you can return to mxsync to continue the synchronization process.
+-------------------------+
| Section 1 of 5 |
| Systems Insight Manager |
+-------------------------+
Populate the HP SIM database with post-backup system changes.
**** Analysis: Run HP SIM discovery to discover post-backup system ****
**** changes. ****
**** Section 1 of 5, phase 1 of 1 ****
HP SIM discovery tasks must be run to discover any post-backup system
changes
that may have occurred.
Run HP SIM
discovery..................................................[INPUT]
ISSUE: The HP SIM database may be out-of-date. To discover
changes that may have occurred after backup, HP SIM
41