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

5. Start the Insight Management services described in Table 2 in the reverse order

described by the Stop Order column (with the exception of the Insight Control server

deployment services, which should be started in the order listed). You can do this using

the mxsync-svcutil script, located in <SIM>\mxsync\bin.

mxsync-svcutil start

For HA CMS configurations, you will also need to start the Insight Management services

that are running on the secondary node. To do this, you must login to the secondary

node. There are two local services that are not configured as part of the Insight

Management cluster service that need to be changed. These services are running on

both cluster server nodes and will need to be changed manually on the secondary

node. You can stop these services from the command prompt using the mxsync-

svcutil script.

6. After backing up a secondary CMS in an infrastructure orchestration federated CMS

configuration, you need to issue the ioexec command on the primary CMS to resume

operations targeted at the secondary CMS that was just backed up. You must provide

the lowercase FQDN of the secondary CMS to be backed up. This must be the same

hostname configured on the Federated CMS Configuration page. You can get to the

page by selecting Federated CMS Configuration… from the Options menu on the primary

CMS.

ioexec endmaintenance cms –C <secondaryCmsFQDN>

For more information about this command, run ioexec endmaintenance cms -–help.

7. HP recommends scheduling a Windows task to frequently save the HP Matrix

infrastructure orchestration network definition files between backups. These files contain

the current status of the infrastructure orchestration networks and are stored in the

<HPIO>\data\ directory. There is one XML file, Subnet_<network name>.xml, for each

network. During the restore process, it will be possible to use these files to reduce the

effort required to identify the IP addresses that were allocated after backup.

Note:

To support automatic provisioning, HP Matrix infrastructure

orchestration maintains a pool of available IP addresses for each

network defined in infrastructure orchestration. After restore, IP

addresses allocated after the last backup, but before the

catastrophic failure occurred, will be incorrectly marked in the

restore database as available and need to be fixed up. For

additional details, see the mxsync Matrix infrastructure orchestration

Synchronization Section section in Appendix A: HP Insight mxsync

Utility man page.