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

Logical servers and associated SAN-based Storage section

During this section, the restored Logical Server Management (LSM) and the HP Storage

Provisioning Manager (SPM) databases are resynchronized with the state of the Virtual

Connect profiles, virtual machines, and storage volumes on the managed devices.

During the first phase, the mxsync tool updates the presentation state of the storage

volumes in the restored HP Storage Provisioning Manager (SPM) database to reflect the

actual state of the storage volumes in the storage array. The tool starts the HP Extenisble

Storage & Server Adapter. It starts the HP SPM Storage Module J2EE Service and HP SPM

Storage Module Service Windows services, which need to be running prior to starting the HP

Storage Provisioning Manager Service Windows service. The mxsync tool instructs you how

to place the HP Storage Provisioning Manager Service Windows service in Internal Recovery

mode by editing the file <SPM>\state\ApplicationConfig.xml to change the

<RecoveryMode> property to InternalRecovery. It then starts the HP Storage Provisioning

Manager Service Windows service. At this time, you are instructed to check the SPM

browser-based interface at https://<servername>:8000 to determine when the Storage

Provisioning Manager 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 or remove resources, including Arrays, Storage Pools, Volumes, and Networks, that

were imported or removed 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 interface as “offline” and have names that start

with SPM_.

Note:

The SPM Internal Recovery phase 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. This is

done to prevent the presentation state from being accidently

changed during the recovery process.