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

Technical white paper | HP Insight Management 7.3
Note:
For HA CMS cluster configurations, HP Insight Management services configured as cluster resources should remain set to
Manual
. The command mxsync-svcutil auto will change the startup type only for HP Insight Management services
that are not configured as cluster resources.
5. Start the HP Insight Management services described 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 cluster configurations, some local services are not configured as part of the HP Insight Management cluster
service; they need to be stopped on both nodes. These services are started automatically on the primary node by the
start command. The services must be started manually on the secondary node. To do this, you must log in to the
secondary node and start the services by running the mxsync-svcutil script (if installed locally) from the command
prompt.
Note:
For RDP, pending jobs for all targets were moved to the “Do not schedule” state. Use RDP console to reschedule jobs.
6. After backing up a secondary CMS in an infrastructure orchestration federated CMS configuration, you must issue the
ioexec command 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. 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>
For more information about this command, run the command 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, these files can be used to reduce the effort required to identify the IP addresses
that were allocated after the 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 the restore, IP addresses allocated after the last backup, but
before the catastrophic failure, will be incorrectly marked in the restore database as available, and will need to be corrected.
For details, see the mxsync
Matrix infrastructure orchestration synchronization
section in Appendix A: mxsync man page.
Table 5. HP Insight Management service names
HP Insight Management
component
Service display name Service name
HP Matrix infrastructure
orchestration
HP Matrix infrastructure
orchestration
hpio
HP Matrix infrastructure
orchestration
HP Matrix infrastructure
chargeback
chargeback
HP Matrix infrastructure HP Matrix infrastructure bursting hpio-connecter
13