HP Insight Management 7.3 DMT White Paper
Technical White Paper | HP Insight Management 7.3
a. Navigate to the HP Matrix Recovery Storage Management Servers tab.
b. Select 3PAR Storage Management Server, and click Edit.
c. Click Save without changing any data.
4. Perform a rehearsed failover.
For validation of the migration, HP recommends performing a planned failover as outlined in
Chapter 8 of the Matrix OE Recovery Management User Guide.
Step 12: Reconfiguring Insight Control server deployment agents
If you had customized deployment jobs on the source CMS, you must import them to the target
CMS. Copy the exported job files from the safe location and any other customized script files to
the target CMS. To import the customized jobs on the target CMS:
1. From the deployment console menu, select FileImport/ExportImport Jobs…
2. Browse to the local copy of the jobs file that was previously exported from the source
CMS.
3. Select a job folder in which to import the jobs.
4. Press OK to begin the import process.
5. Copy any customized deployment script files from the safe location to the appropriate
locations on the target CMS.
If the deployment server is remote, you will need to change the location where HP SIM looks for
the deployment server.
1. Open a command prompt and run mxnodesecurity –l to list the deployment
server IP address. If this address is correct you can stop here.
2. To change the IP address used by HP SIM for the deployment server, type the following in
the same command window:
a. mxnodesecurity -r -p dsc_rdp -n <rdp-ip> to delete the old
deployment server IP address where <rdp-ip> is the IP address of the
deployment server.
b. mxnodesecurity -a -p dsc_rdp -c username:password -n
<rdp-ip> to add the new deployment server IP back in with the user name
and password necessary to access that server.
Step 13: Reinstalling and reconfiguring Insight Remote Support
Insight Remote Support Advanced must be reinstalled and reconfigured on the target CMS. For
more information, see the HP Systems Insight Manager 7.3 Installation and Configuration Guide
for Microsoft Windows.
If the source CMS had IRSA installed and configured in it, then the target CMS should also have
IRSA installed and configured for successful import.
45