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

Technical white paper | HP Insight Management 7.3

Completing the recovery process

Changes to managed resources that occur after the backup but before the failure (referred to as

post-backup activity

) can

affect the recovery process. Examples of post-backup activity include activating or deactivating a logical server or

infrastructure orchestration service, deleting an infrastructure orchestration service or logical server, and adding or deleting

a recovery management recovery group. To complete the recovery process, the HP Insight Management components must

be resynchronized.

Important:

If you are using the CMS to manage gWLM on Integrity servers

: If, as a post-backup activity, changes were made to SRDs,

policies, or workloads, additional steps are required to synchronize the state of the restored gWLM database with the

configuration deployed on the gWLM managed systems. Before you proceed, see Appendix F: gWLM configuration changes.

To avoid the manual steps required to perform the resynchronization, HP strongly recommends backing up the

environment whenever gWLM configuration changes are made.

Note:

The purpose of the mxsync tool is to place the HP Insight Management components in a consistent state. Operations

issued after the backup may need to be manually re-entered or cleaned up. HP recommends backing up the environment

frequently.

1. Run the mxsync command-line utility in execution mode (-e), and follow the displayed instructions.

mxsync -e

The mxsync tool is an aid to guide the Administrator through the process of synchronizing the HP Insight Management

environment with the current state of managed resources. Appendix A: mxsync man page contains a description of the

mxsync tool. Appendix B: Sample mxsync.log contains sample output from the mxsync command.

Notes:

• The installation directory for the mxsync tool is <SIM>\mxsync\bin. The fully qualified path for the mxsync

command is <SIM>\mxsync\bin\mxsync.

• If, as a post-backup activity, a VC Domain was added to or removed from a VC Domain Group, the Add VC

Domain/Remove VC Domain operation must be reissued to synchronize the state of the VC Domain with the restored

VCEM database. If, as a post-backup activity, VC modules were added or removed, the operation must be reissued to

synchronize the state of the VC Domain with the restored VCEM database. To avoid the manual steps required to

perform the resynchronization, HP strongly recommends backing up the environment whenever these changes occur.

Appendix E: VCEM resynchronization actions

describes the steps required to reissue these operations.

2. Verify that the startup type for the HP Insight Management services is set to

Automatic

. Table 9 provides a list of the

HP Insight Management service display names. To verify the startup type, enter the following command at the

command prompt:

mxsync-svcutil auto

For HA CMS cluster configurations, you may also need to change the startup type for the Insight Management services

running on the secondary node. There are two local services, running on both cluster nodes that are not configured as

part of the HP Insight Management cluster service. You can change the startup type of these services by running the

mxsync-svcutil script from the command prompt on the secondary node.