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

Technical white paper | HP Insight Management 7.3
3. After all mxsync synchronization phases have completed successfully, you can start the HP Insight Management
services described in Table 9 in the reverse order listed in 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 by using the
mxsync-svcutil script as shown in Table 10. Depending on your configuration, several of these services may have
been started during execution of mxsync. Enter the following command from the command prompt:
mxsync-svcutil start
For HA CMS cluster configurations, some local services are not configured as part of the HP Insight Management cluster
service; they must be stopped on both nodes. These services are started automatically on the primary node by the
start command. They must be started manually on the secondary node. To do this, you must log in to the secondary
node and start these services by running the mxsync-svcutil script (if installed locally) from the command prompt.
Note:
For RDP, pending jobs for all targets were moved to the “Do not schedule” state. Use RDP console to reschedule jobs.
4. You may need to re-enter MAC/WWN exclusion-range configuration changes that were made in VCEM after the backup.
For example, if an exclusion range was removed after the backup, you must re-enter the change.
5. You may need to perform the following manual steps to resynchronize logical servers that were modified after the
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. In Systems Insight Manager, select
Tools

HP Matrix OE
visualization
. From the
Logical Servers
perspective, select the logical server to be deleted by selecting
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
.
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
Tools

HP
Matrix OE visualization
in Systems Insight Manager. Select the blade hosting the corresponding VC profile, then
select
Tools

Logical Servers

Import
in the Virtualization Manager.
Note:
If a VC-based logical server created after the backup was inactive when the failure occurred, the VC profile definition will be
lost and the logical server must be re-created.
C. If a logical server definition was modified after the backup (Identity, Compute, Storage, or Network), the changes
must be re-entered manually after the resynchronization has completed successfully.
6. You may need to perform the following manual steps to resynchronize storage pool entries that were modified or
added after the backup:
A. If a catalog-based storage pool entry was deleted as a post-backup activity, you may need to manually
delete the storage pool entry definition from the Matrix OE database. In Systems Insight Manager, select
Tools

HP Matrix OE visualization
. Select
Modify

Logical Server Storage Pools
. On the
Manage Storage
Pool
page, click the
Remove
button for the storage pool entry that was deleted after the backup.
B. If a catalog-based storage pool entry was modified to add an unmasked storage volume as a post-backup
activity, you must manually re-enter the changes after resynchronization has completed successfully. In
Systems Insight Manager, select
Tools

HP Matrix OE visualization
. Select
Modify

Logical Server Storage
Pools
. From the
Manage Storage Pool
page, click the
Modify
button for the storage pool entry that was
modified after the backup. Then, re-add the unmasked storage volume.
C. If a logical server with at least one data volume was created as a post-backup activity, or if a storage pool
entry with at least one data volume was added to an existing logical server as a post-backup activity, the
logical server may no longer contain information about the data volumes after the mxsync or manual
import of the logical server. If no storage pool entry for this logical server existed before the backup, the
import (or refresh) will generate a single embedded storage pool entry using the information contained in
the VC profile. The disk information will need to be added manually to the embedded SPE. In Systems Insight
Manager, select
Tools

HP Matrix OE visualization
. Select
Perspective

Logical Server
. Select the check box
28