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

completes its internal refresh and transitions to Manual Recovery Mode. This can be seen in

the top right corner of the page.

The final step in this phase is to manually re-enter manual changes (add, remove, and

updates) that were made as post-backup activity in the following areas:

• Local users and registered certificates

• Role Definitions

• Security Groups, access rights, members of security groups

• Templates

• Import/evict resources, including Arrays, Storage Pools, Volumes, and Networks, that were

created or deleted post-backup.

Note:

At this time, you should also remove any volumes in SPM for which

there is no corresponding volume on the array. This can occur for

volumes that were deleted as post-backup activity when using the

new 7.0 auto-provisioning feature. These are marked in the SPM

browser-based interfaces as “offline” and have names that start

with SPM_.

Note:

During SPM Internal Recovery, SPM compares the presentation state

of the storage volumes stored in the SPM database with the actual

state of the volumes in the managed arrays. If the presentation

state of a storage volume has changed, SPM will put the volume

into Quarantine, disabling automation for the storage volume.

Quarantine and Manual Recovery mode prevent the presentation

state from being accidently changed during the recovery process.

During the second phase, the logical server refresh operation is executed. The logical

server refresh operation analyzes and, if necessary, repairs the logical server definitions in

the restored Matrix Operating Environment database to ensure consistency with the

underlying Systems Insight Manager, VMM, and VCEM definitions. First it verifies that the HP

Extensible Storage & Server Adapter, the HP SPM Storage Module J2EE Service

, the HP SPM

Storage Module Service, and the HP Storage Provisioning Manager Service Windows services

are running. Then it starts the HP Logical Server Automation Windows service and invokes the

refresh operation. The actions taken by the logical server refresh operation are written to

<VSE>\logs\vselog.lsm.log. Logical server refresh log entries contain the tag

[LSM_REFRESH_EVENT].

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 or 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 three phases in this section.