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

Technical white paper | HP Insight Management 7.3
Note:
To support automatic provisioning, HP infrastructure orchestration maintains a pool of available IP addresses for each
network defined in infrastructure orchestration. After restore, IP addresses allocated after the last backup, but before the
catastrophic failure occurred, are incorrectly marked as available and must be fixed.
During the third phase, you are given the opportunity to update the status of the dynamic and static IP addresses allocated
to the defined infrastructure orchestration networks. To help with this effort, the mxsync tool creates a file,
<SIM>\mxsync\data\IPAddresses.txt, containing a list of the allocated IP addresses. Prior to performing the
execution step, you are asked to edit the generated file to identify any IP addresses that were allocated after backup.
Note:
If you have provided a more recent version of the HP Matrix infrastructure orchestration network files,
<HPIO>\data\Subnet_<network name>.xml, you only need to identify IP addresses that were allocated since the
network files were backed up.
During the fourth phase, the mxsync tool starts the required infrastructure orchestration services. This is needed for the
next section of mxsync, if recovery management is using IO-based recovery group, and so that remaining manual recovery
steps can be performed and normal operations can resume.
Mxsync Matrix recovery management synchronization section
During this section, the restored HP Matrix recovery management database is updated. There are two phases in this section.
The first phase is to synchronize logical server based recovery groups with LSM. The second phase is to synchronize
infrastructure orchestration based recovery groups.
To reduce the effort required to re-create the post-backup recovery management configuration changes, you are given the
opportunity, in phase one, to import an exported recovery management configuration file. If changes have been made in the
recovery management configuration post backup, this option is highly recommended, otherwise such changes need to be
manually re-entered. This option is only necessary if recovery management has been configured.
Import option
If the import option is chosen, you are asked to provide an exported recovery management configuration file and copy this
file to <HPRM>\conf\mxsync_config on the local site. For details about creating an export file, see the HP Matrix
recovery management Online Help.
If you are importing from an exported recovery management configuration file generated at the remote site, you must
describe the mapping between the logical server names on the remote site and the local site. To help with this effort, the
mxsync tool creates a file, <HPRM>\conf\mxsync_lsnames.txt, containing a list of <recovery group name, remote
logical server name and local logical server name> triples. You must edit this file to include the local logical server name. If
the recovery group no longer exists (it was deleted post-backup), the local logical server name must be left blank.
During the analysis step, the mxsync tool generates a file, <HPRM>\conf\mxsync_fixups.txt, containing the
recommended resynchronization actions. Potential actions include resetting the site role for Recovery Groups if any have
changed since the backup or export file was generated, deleting a recovery group that may have been removed as a post-
backup activity, and updating the membership of recovery groups. You are given the opportunity to edit this file before
proceeding with the execution step. You can reset the site role by selecting
HP Matrix recovery management …
from the
Tools
menu in Systems Insight Manager, then clicking the
Activate…
or
Deactivate…
button from the
Site
tab and selecting
the Recovery Groups to activate or deactivate at the local site.
For the second phase, recovery management synchronizes recovery groups for infrastructure orchestration services. The
same configuration file (export file), if provided in the first phase, will be used to obtain the latest recovery group
configuration. If an RM-protected infrastructure orchestration services was deleted as a post-backup activity, the mxsync
tool will automatically remove it from the recovery group to which it belongs
37