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

Technical white paper | HP Insight Management 7.3

The activation status of a recovery group set depends on the restored database or, if an export file was used, whether the

export file was created on the local or remote CMS. You can change the status of a recovery group set by uncommenting the

line and specifying yes or no in the

Activated at Local Site

field before proceeding to the execution phase.

Figure 5: Contents of the mxsync_fixup.txt file

In the second section of the

Matrix recovery management

section, you are given the opportunity to update the

infrastructure orchestration-based RM recovery groups. In this example, the recovery group RG2 contained the HP IO service

TC10. This service was deleted as a post-backup activity. Since mxsync could not find the HP IO service, it updated the

recovery group to remove the service. At that point, the recovery group was empty, so mxsync deleted the recovery group.

# The recovery group state (Activated at Local Site) can be set by the Administrator

# if he/she wish to change it in the restoring site. All the recovery groups in a site

# pair (Preferred site, Secondary site) will be set to the same state, as specified by

# the Administrator in the below lines. The Administrator needs to uncomment each site pair

# to specify the desired state of the recovery groups in that set. The desired state can be

# yes or no. The state yes means, the recovery groups are active and enabled in the restoring

# site. The state no means, the recovery groups in that set are deactivated and disabled in the

# restoring site.

# The following lines show all the recovery group sets found in the configuration.

# If the user doesn't uncomment and specify the desired state (yes/no), for Activated at Local Site,

# then the Mxsync will use the state that exists in the current configuration if the

# configuration was obtained from the local node or local database. If the configuration is

# obtained from a remote node, then the state of the recovery groups will be reversed.

# Please ensure a tab separates the Secondary site name and the desired state.

# Recovery_Group_Set Preferred site Secondary site Activated at Local Site(yes/no)

#Recovery_Group_Set RG1 RG2

# Mxsync could not validate the following Logical Server(s).

# If the reason is that the Logical Server cannot be located, you may provide a fix by bringing the

# Logical Server into existence (e.g., via 'import Logical Server' operation) or request deletion

# the logical server in the recovery group by deleting the line listing the logical server.

# If the reason is that Logical Server configuration is missing in the Recovery Group, you must

# request deletion (else you must redo the analysis and supply a local Logical Server name for this

# Recovery Group.)

# Note that if you request deletion of all Logical Servers present in a Recovery Group, the execute

# step will present the requested deletions as a single fixup, namely the deletion of the Recovery

# Group as a whole.