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

34
during the logical server refresh operation, you must issue an unmanage request
by selecting Unmanage Logical Server… from the Delete menu.
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 will need to 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 new infrastructure
orchestration server may be lost. If so, you can take the following steps to
recreate the logical server definition and re-establish the connection.
i. If the infrastructure orchestration server is active, you will need to
manually import the server as a logical server using the same logical
server name that was assigned by the HPIO server when it was originally
created.
Note:
The server may have been automatically
imported 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 will need to
rename the logical server to match the HPIO
defined logical server name.
ii. If the infrastructure orchestration service is VM-based and inactive, you
will need to first manually re-add the virtual machine to the vCenter
inventory. Once the virtual machine has been discovered by VMM, you
will need to manually import the VM as a logical server using the same
logical server name that was assigned by the HPIO server when it was
originally created.
iii. 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 add a new server to the service, or delete the service and re-
provision the service if there is only one server for the service.
c. If an infrastructure orchestration service definition was modified after backup
(Change Lease Period), these changes must be manually re-entered after
resynchronization has successfully completed.
9. If you have restored and resynchronized the primary site CMS for Matrix recovery
management configurations, you must ensure the recovery site is updated to reflect
the changes made to the primary Matrix recovery management site configuration. For
details of how to export and import recovery management configuration data, see the
HP Matrix recovery management Online Help.