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

26
Directory or File Optional Description
<WMIMapper>\ssl.cfg
No OpenPegasus WMI Mapper
configuration file
2. Using the tool of your choice, perform a full backup of the databases listed in Table 8.
The database backup must be sufficient to restore the entire database, including
schema as well as data. If Insight Management has been configured to use a remote
database, perform this action on the remote database server.
Table 8. Insight Management databases
Component Database Comments
HP Systems Insight Manager
HP Virtual Connect Enterprise Manager
HP Insight managed system setup wizard
Insight_v* For example,
Insight_v50_0_5037457.
HP Insight Control performance
management
PMP_V* For example, PMP_V5_0.
HP Insight Control server deployment
eXpress
The eXpress database
should only be backed up
or restored during a full
system backup.
HP Insight Control virtual machine
management
Hpvmmsqldb
HP Matrix capacity planning, configuration
and workload management
gwlm
HP Matrix infrastructure orchestration hpio
HP Matrix infrastructure orchestration oo
HP Matrix recovery management lsdt
Security Note:
The archived files and databases contain confidential information
including credential data. Access to this data should be carefully
controlled.
3. 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, as follows:
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 started. 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.
4. After backing up a secondary CMS in an infrastructure orchestration Federated CMS
configuration, you need to issue the ioexec command from the command prompt on
the primary CMS to resume operations targeted at the secondary CMS that was just
backed up. You will need to provide the lowercase FQDN of the secondary CMS to be