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

ManualsBrandsHP ManualsSoftwareHP Insight Control

Technical white paper | HP Insight Management 7.3

If, as a post-backup activity, a VC Domain was removed from a VC Domain Group and re-added to the same or a different VC

Domain Group, you must manually reissue the

Remove from VC Domain Group

operation, remove the external manager

account (see the section "Removing an external manager account" in the VCEM User Guide), and reissue the

Add to VC

Domain Group

operation. If, as a post-backup activity you updated the VC firmware in any VC Domain managed by VCEM,

additional steps may be required before you can successfully complete phase 2. See

Appendix E: VCEM resynchronization

actions for additional details.

For handling of disabled enclosures during mxsync, see Appendix E: VCEM resynchronization actions for additional details.

mxsync Logical servers and associated SAN-based storage synchronization section

During this section, the restored HP Matrix Operating Environment and HP Storage Provisioning Manager databases are

updated.

There are three phases in this section.

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 Extensible Storage & Server Adapter

Windows service. Then the mxsync tool instructs you how to place the

Storage Provisioning Manager

Service

Windows service in InternalRecovery mode by editing the file

<SPM>\state\ApplicationConfig.xml to change the <RecoveryMode> property to InternalRecovery.

Once it verifies the recovery mode setting, it 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 (adds, removes, 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 created or

deleted post-backup

Note:

• SPM utilizes management signatures to help the administrator determine which volumes should be imported and

which volumes can be removed at this time. The volumes that were imported post-backup have “Previously imported

by this SPM instance” in the Notes field of the Import Volume Wizard. See Appendix G: SPM resynchronization actions

for additional information.

• During SPM

Internal Recovery

, SPM puts all volumes in its restored catalog into quarantine. Quarantine and

Manual

Recovery

mode disables automations and prevents the presentation state of the volume on the array 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

, 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].