HP Insight Management 7.3 Installation and Configuration Guide

6. Switch between HP Server Automation (SA) cores
IO 7.2 supports Insight Control server deployment 7.2 by default. To configure any version
of SA support, copy the client library from the Server Automation core:
a. Replace the file opswclient.jar from the 9.x SA Core found at <SIM Installation
Directory>\lib\ with the file of the same name from the SA Core to be configured
with installed Matrix Operating Environment. The location of opswclient.jar can be found
on the SA Core at /opt/opsware/da/webapps/arm/WEB-INF/lib/
opswclient.jar and at /opt/opsware/twist/extlib/client/
opswclient.jar.
To replace the opswclient.jar file with one copied from your SA core server using secure
copy, enter the following two commands at the CMS command line:
NOTE: The user must have write credentials for the lib directory, and remember to
include the space and period at the end of the second command. If you backup the local
opswclient.jar file before using secure copy, you must move the backup copy out
of the lib directory.
b. Remove the existing SA Core credentials and add the new SA Core credentials to the HP
SIM server using the mxnodesecurity utility.
c. Restart the Systems Insight Manager Windows service.
Performing server migrations
If you installed Insight Control server migration, you can use it to migrate an operating system,
applications, and data from one server to another, instead of manually redeploying these elements
on a new server.
You can perform the following server migrations using Insight Control server migration:
Physical-to-ProLiant (P2P)—Migrates a physical machine to a ProLiant server
Physical-to-virtual (P2V)—Migrates a physical machine to a virtual machine guest in a virtual
machine host
Virtual-to-ProLiant (V2P)—Migrates a virtual machine guest in a virtual machine host to a
ProLiant server
Virtual-to-virtual (V2V)—Migrates a virtual machine guest between virtualization layers
Here is a synopsis of the steps you must perform for server migration; the order of these steps vary
depending on the migration type. For complete information about performing server migrations,
see the HP Insight Control Server Migration User Guide at the following website:
http://www.hp.com/go/insightcontrol/docs
1. Identify the source server.
2. Select volumes to migrate.
3. Identify the destination server or virtual machine host.
4. Assign source disks to destination disks and resize partitions.
5. Test the network connection.
6. Select additional migration options.
7. Confirm migration details.
8. Review the migration progress.
Performing server migrations 59