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

Appendix I: HA CMS cluster configurations

This appendix provides additional information for taking full system and partial backups of

your Insight Management CMS. When the CMS is in an HA cluster configuration, there are

some differences that need to be considered.

When stopping and starting Insight Management services as part of the backup or restore

process, it is important to use mxsync-svcutil or the Failover Cluster Manager for most of

these operations. Most Insight Management services are configured as cluster resources

and they need to be stopped and started (or taken offline and put online) through the

cluster manager. If you stop an Insight Management service using a non-cluster aware

mechanism, such as net stop, a failover of the Insight Management cluster service may

occur. The following Insight Management services are not configured as cluster resources

and run locally on both servers in the cluster: HP System Management Homepage, HP

Version Control Agent, Pegasus WMI Mapper Indications Service.

Note:

For HA CMS configurations, you will need to manually copy the

mxsync-svcutil.bat script to the local disk of each cluster node.

The file layout for HA CMS cluster configurations is slightly different than what is described in

this document. In an HA CMS cluster configuration, most of the Insight Management

program and data files are located on a shared volume (for example, the V:\ drive). This

layout makes it possible for either server in the cluster to host the Insight Management

cluster service. Similarly, the databases reside on a separate shared volume or are hosted

external to the cluster. However, there are some files that reside on the local boot volumes

of the two cluster servers, referred to as local files. These files are listed in Table 19.

For HA CMS cluster configurations, the full backup needs to include all parts of the cluster,

including the cluster configuration, all shared disks, and the local boot disks of the two

servers in the cluster. HP recommends that you follow the documented procedures

available from Microsoft for backing up and restoring Microsoft Failover Clusters. The

backup should be taken using a cluster-aware backup tool, in case the cluster

configuration needs to be restored from backup.

Note:

For HA CMS cluster configurations, HP recommends that you follow

the recommended backup procedures from Microsoft for doing a

full backup of the cluster nodes and cluster configuration. See the

Microsoft documentation for additional details:

http://technet.microsoft.com/en-us/library/cc771973.aspx

For partial backups, it is not sufficient to back up the specific files and directories from the

server that is currently hosting the Insight Management cluster service, along with the

Insight Management databases. There is a subset of files that reside on both servers’ boot

disks. You will also need to back up this set of local files, listed in Table 19, on the other server

in the cluster. The local services on the other server in the cluster do not need to be

stopped prior to backup.

In the event of a restore, it is important to keep all four datasets in sync: Insight

Management data directories and files, Insight Management databases, local Insight

Management data directories and files on each of the two servers in the cluster. When