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

32
Note:
If, as a post-backup activity, a VC Domain was added to or
removed from a VC Domain Group, the Add VC Domain/Remove
VC Domain operation will need to be reissued to synchronize the
state of the VC Domain with the restored VCEM database. If, as a
post-backup activity, VC modules were added of removed, the
steps to perform the operation will need to be reissued to
synchronize the state of the VC Domain with the restore VCEM
database. To avoid the manual steps required to perform this
resynchronization, HP strongly recommends backing up the
environment whenever these changes occur. Appendix E: VCEM
resynchronization actions
contains a description of the steps
required to reissue these operations.
2. Verify that the startup type for the HP Insight Management services is set to Automatic.
Table 9 provides a list of the HP Insight Management service display names. You can
accomplish this by executing the following command from the command prompt:
mxsync-svcutil auto
For HA CMS configurations, you may also need to change the startup type for the Insight
Management services that are running on the secondary node. There are two local
services, running on both cluster nodes that are not configured as part of the Insight
Management cluster service. You can change the startup type of these services using
from the command prompt the mxsync-svcutil script on the secondary node.
3. After all mxsync synchronization phases have completed successfully, you may now start
the Insight Management services described in Table 9 in the reverse order defined by
the Stop order column (with the exception of the Insight Control server deployment
services, which should be started in the order listed). You can do this using the mxsync-
svcutil script as shown in Table
10. Depending on your configuration, several of these
services may have been started during the execution of mxsync. Execute the following
command from the command prompt:
mxsync-svcutil start
For HA CMS configurations, you will also need to start the Insight Management services
that are running on the secondary node. There are two local services running on both
cluster nodes that are not configured as part of the Insight Management cluster service.
You can start these services from the command prompt using the mxsync-svcutil
script on the secondary node.
4. You may need to re-enter VCEM MAC/WWN exclusion range configuration changes
that were made after backup. For example, if an exclusion range was removed after
backup, this action will need to be performed again.
5. You may need to perform the following manual steps to resynchronize logical servers
that were modified after backup.
a. If a logical server was deleted as a post-backup activity, you may need to
manually delete the logical server definition from the restored Matrix OE
database. Select HP Matrix OE visualization… from the Tools menu in Systems
Insight Manager. From the Logical Servers perspective select the logical server to
be deleted. Select Delete Logical Server… from the Delete menu. If the logical
server definition was marked Inoperable during the logical server refresh
operation, you must issue an unmanage request by selecting Unmanage Logical
Server… from the Delete menu.
b. If a logical server was created as a post-backup activity, you may need to
manually import the logical server to add the definition to the restored Matrix OE
database. You can import the logical server by selecting HP Matrix OE