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

38
Section Phase Synchronization activity
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.
RM
1
Use an up-to-date RM configuration export file to install any
post-backup RM configuration changes. If any protected
logical servers have been deleted, update the corresponding
RM recovery groups as necessary.
The mxsync tool supports two modes of operation, an analysis-only mode and an
execution mode. By default, mxsync runs in an analysis-only mode. When started in
an analysis-only mode, all execution steps are skipped and no updates are made
to the restored databases or files. The analysis-only mode is used to preview the
recommended changes for the next synchronization phase.
Warning:
When run in analysis-only mode, an unresolved issue in one phase
can cause subsequent analysis phases to report incomplete or
incorrect results.
Warning:
When run in execution mode, all issues identified in a phase must
be resolved before proceeding to the next phase.
mxsync initialization
As a general rule, the Insight Management Windows services should not be running during
the execution of mxsync. However, the mxsync tool does depend on several HP Insight
Management Windows services to perform the analysis and execute steps. Prior to starting
the synchronization activity, the mxsync tool checks the status of the Insight Management
services and recommend actions for stopping and starting services.
When run in execution mode, if you respond “y” to the prompt to make the recommended
changes, the required services are started and the non-required Insight Management
services are stopped. For HA CMS cluster configurations, mxsync will start and stop the
required services as cluster resources.
When run in analysis-only mode, the mxsync tool does not make any changes to the
running state of the Windows services. If the required services are not started, the mxsync
tool exits with an error. You must manually start the services to run mxsync. If non-required
services are running, mxsync allows the analysis to proceed. However, a warning is
displayed stating that in-progress operations may cause mxsync to report non-existent
issues. If issues are identified when the system is quiesced, the services should be stopped
and the analysis rerun.