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

Technical white paper | HP Insight Management 7.3
Appendix A: mxsync man page
This appendix contains the HP Insight Management mxsync tool man page. Appendix B: Sample mxsync.log provides
sample output from the mxsync command. To run mxsync, you must be logged on to the CMS using a Windows account
with Administrator privileges; it must also be a valid Systems Insight Manager Administrator account. On Microsoft Windows
Server 2008/2012, you must run mxsync as Administrator.
NAME
mxsync - eases the task of synchronizing an Insight Management CMS environment that has been restored from backup
with the state of the managed resources. This utility can be used to identify potential inconsistencies, recommend corrective
actions, and perform most recommended actions.
SYNOPSIS
mxsync [--help] [--version] [-e] [-c]
DESCRIPTION
If the HP Insight Management central management server (CMS) environment becomes lost or corrupted, it is necessary to
restore the environment from a backup copy. The mxsync tool guides the Administrator through the process of
synchronizing an Insight Management CMS environment that has been restored from backup with the state of the managed
resources.
The mxsync tool is divided into five sections that are executed sequentially in the following order: HP Systems Insight
Manager (SIM), Virtual Connect Enterprise Manager (VCEM), Logical servers and associated SAN-based storage (LSM), HP
Matrix infrastructure orchestration (HP IO), and HP Matrix recovery management (RM). Each section is responsible for
identifying inconsistencies between its representation of a resource and that of the underlying layer. A section consists of
one or more phases. A phase defines an analysis and execution step for a specific synchronization activity.
Table 12. Synchronization activity
Section Phase Synchronization activity
SIM
1 Discover any system changes that may have occurred after backup was performed.
VCEM
1
Ensure WWN and MAC address assigned to a VCEM profile have not been reassigned to a different
VC profile. Ensure WWN and MAC addresses allocated to VC profiles, after backup, have been
correctly marked as “External” in the VCEM database.
2 Resynchronize each VC domain managed by VCEM.
LSM
1
Start the HP Extensible Storage & Server Adapter Windows service. Put SPM into recovery mode.
Start the HP Storage Provisioning Manager Windows service. Perform a recovery-mode refresh
of all SPM catalog entries. Import into SPM any arrays and volumes that were imported after the
backup.
2
Start the HP Logical Server Automation Windows service. Wait for the refresh operation to
complete.
3
Run the lsmanalyzer tool. Review and perform recommended manual recovery steps. Verify all
issues reported by lsmanalyzer have been resolved. Take the HP Storage Provisioning Manager
service out of recovery mode.
HP IO
1
Terminate HP IO requests that were in-progress when the backup was taken or requests that
were scheduled to run after the backup but before the restore. This is necessary to prevent the
HP Infrastructure Orchestration Windows service from attempting to restart a request that may
have already completed.
2
Update the HP IO database to remove the definition of HP IO services that were deleted post-
backup.
3 Update the HP IO database to mark, as allocated, any IP address that was allocated after backup.
4
Start HP Matrix infrastructure orchestration Windows services: HP Matrix infrastructure
orchestration, RSCentral, and RSJRAS.
RM
1
Update RM state with underlying logical server state. Optionally, use an up-to-date RM
configuration export file to recover any post-backup RM configuration changes. If any protected
logical servers have been deleted, update the corresponding RM recovery groups.
32