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

Technical white paper | HP Insight Management 7.3

Component Database Comments

HP Matrix Operating Environment capacity planning,

configuration, and workload management

gwlm

HP Matrix infrastructure orchestration hpio

HP Matrix infrastructure orchestration oo

HP Matrix infrastructure orchestration HPMOEMetering

HP Matrix recovery management lsdt

Important:

The archived files and databases contain confidential information, including credential data. Access to this data should be

carefully controlled.

3. Start the HP Insight Management services listed in Table 3 in the reverse order listed in 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 by using the mxsync-svcutil script, located in <SIM>\mxsync\bin:

mxsync-svcutil start

For HA CMS configurations, some local services are not configured as part of the HP Insight Management cluster

service; they must be stopped on both nodes. These services are started automatically on the primary node by the

start command. They need to be started manually on the secondary node. To do this, you must log in to the secondary

node, and start these services by running the mxsync-svcutil script (if installed locally) from the command

prompt.

4. After backing up a secondary CMS in an infrastructure orchestration federated CMS configuration, you must run the

ioexec command from the command prompt on the primary CMS to resume operations targeted at the secondary

CMS that was 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. To access this page, select

Options



Federated CMS Configuration…

on the primary CMS.

ioexec endmaintenance cms –C <secondaryCMSFQDN>

5. 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 directory <HPIO>\data. There is one XML file, Subnet_<network name>.xml, for each

network. During the restore process, these files can be used to reduce the effort required to identify the IP addresses

that were allocated after the backup.