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

Technical white paper | HP Insight Management 7.3
for the logical server, and then select
Modify

Logical Server
. On the
Storage
tab, click the
Modify
button for
the SPE. Click the
Add Volume
button, and then provide the details, such as the
Storage Port WWN
and
LUN
,
for each missing volume.
7. After restoring a secondary CMS in an infrastructure orchestration federated CMS configuration, you must issue the
following command from the command prompt on the primary CMS to resume operations targeted at the secondary
CMS that was backed up:
ioexec endmaintenance cms –C <secondaryCMSFQDN>
8. You may need to perform the following manual steps to resynchronize the Matrix infrastructure orchestration services.
Note:
The HP Matrix infrastructure orchestration Windows service initiates a refresh on startup. During the refresh, the
infrastructure orchestration database is updated to reflect any state changes that occurred to infrastructure orchestration-
created logical servers when the HP Matrix infrastructure orchestration Windows service was not running. When running, the
service is automatically notified of any state changes.
A. If an infrastructure orchestration service was deleted as a post-backup activity, you can delete that service
from the restored infrastructure orchestration database during execution of mxsync (phase 2 in the
HP
Matrix infrastructure orchestration
section). However, you may need to manually delete the associated
logical server definition by selecting
Tools

HP Matrix OE visualization
in Systems Insight Manager. From the
Logical Servers
perspective, select the logical server to be deleted, and then select
Delete

Delete Logical
Server
. If the logical server definition was marked
Inoperable
during the logical server refresh operation, you
must issue an unmanage request by selecting
Delete

Unmanage Logical Server
.
For infrastructure orchestration federated CMS configurations, this applies to services deleted on the primary
CMS after the backup on the secondary CMS. Upon restore, the Matrix Operating Environment database
restored to a secondary CMS may still contain the associated logical server definitions. These logical server
definitions must be deleted manually from the secondary CMS.
B. If an infrastructure orchestration server was created or added as a post-backup activity, the logical server
may exist as a Matrix Operating Environment logical server, but will no longer be managed as part of an
infrastructure orchestration service.
For infrastructure orchestration federated CMS configurations, if a secondary CMS is being restored, the
logical server definition for the new infrastructure orchestration server may be lost. In this case, perform the
following actions to re-create the logical server definition and to re-establish the connection:
• If the infrastructure orchestration server is active, you must manually import the server as a
logical server using the same logical server name that was assigned by the HPIO server when
it was first created.
Note:
The server may have been imported automatically during a logical server refresh operation. This can happen if the server is
VC-based and associated with a storage pool entry in the restored database. If the server has already been imported, you
must rename the logical server to match the HPIO-defined logical server name.
• If the infrastructure orchestration service is VM-based and inactive, you must manually re-add
the virtual machine to the vCenter inventory. After the virtual machine is discovered by VMM,
you must manually import the VM as a logical server using the same logical server name that
was assigned by the HPIO server when it was first created.
• If the infrastructure orchestration service is VC-based (physical) and inactive, the logical server
and VC profile definitions will no longer be available in the restored database. In this case, you
can leave the existing server definition in the service in an “Unknown” inoperable state, and
29