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

Technical white paper | HP Insight Management 7.3

During the third phase, the mxsync tool runs the lsmanalyzer tool to compare the definitions of the catalog-based

storage pool entries with the state of the volumes in SPM and in the managed arrays. At this time, you are asked to review

the results of the analysis and to perform the recommended manual actions for any issues reported. Once all issues are

resolved, you are asked to take SPM out of recovery mode, either in the SPM interface by clicking

Exit Manual Recovery

editing the file <SPM>\state\ApplicationConfig.xml to change the <RecoveryMode> property to Disabled.

mxsync Matrix infrastructure orchestration synchronization section

During this section, the restored HP Matrix infrastructure orchestration database is updated.

There are four phases in this section.

During the first phase, the mxsync tool analyzes the scheduled, pending approval or in-progress requests. To prevent the

infrastructure orchestration service from attempting to restart requests that may have already completed during the

execution step of this phase, the mxsync tool terminates requests that were in-progress when the backup was taken or

scheduled to run before the restore. The list of requests to be terminated is displayed during the analysis step.

Note:

• Infrastructure orchestration maintains the state of requests in the infrastructure orchestration database. On restart,

the infrastructure orchestration service attempts to restart requests that are in-progress or start scheduled requests

that are past due to run. Because the state of the underlying environment may have changed significantly since the

database was saved, executing, or even cancelling, these requests can have undesirable side-effects (activating or

deactivating production servers, or incorrectly allocating or freeing resources).

During the second phase, you are asked to identify services that have been deleted after backup. To help with this effort, the

mxsync tool creates a file, <SIM>\mxsync\data\InfrastructureServices.txt, containing a list of the

infrastructure orchestration services defined in the restored database. Prior to performing the execution step, you are asked

to edit the generated file and mark with an asterisk (*) the services that were deleted after the backup.

Note:

It is not necessary to identify all post-backup deleted services. Once resynchronization is complete, you can delete orphaned

infrastructure orchestration service definitions by selecting

Infrastructure Orchestration…

from the

Tools

menu in Systems

Insight Manager. From the

Services

tab, select the infrastructure orchestration service to delete and click

Delete

. However, it

is important to identify any post-backup deleted service definitions that include IP addresses that were allocated to another

service. This can happen if as a post-backup activity, a service was deleted, and then a new service was created using one or

more of the IP addresses freed when the service was deleted. If the service definition is deleted after resynchronization, the

IP address is incorrectly marked as available.

During the execution step, the definitions of the deleted services are removed from the infrastructure orchestration

database.