Data migration of an existing Microsoft Windows CMS to a new Insight Software 6.3 system

3. Add the Insight Orchestration Architect users to the HPIO_Architects group.
4. Add the Insight Orchestration regular users to the HPIO_Users group.
Step 10: If using Insight Dynamics recovery management, perform the
following operations
1. From the Insight Recovery user interface on the target and remote site CMS, navigate to the Sites tab,
ensure that the CMS name of the target CMS is properly reflected in either the local or remote site
after migration. If any of the CMS names for the local or remote site is incorrect or blank, update the
site with the correct CMS name. Follow the procedure outlined in Chapter 3 of the Insight Dynamics
Recovery Management User Guide for editing a site.
2. Use the following procedure to refresh the credentials for each EVA Storage Management Server:
a. Navigate to the HP Insight Recovery Storage Management Servers tab.
b. Select an EVA Storage Management Server, and click Edit.
c. Select the Refresh SIM Password box, and then click Save.
3. Perform a rehearsed failover.
For validation of the migration, HP recommends performing a planned failover as outlined in Chapter 8 of the
Insight Dynamics Recovery Management User Guide.
Note:
HP Insight Dynamics recovery management currently has a limitation that job
information is not migrated to the target CMS. Therefore, the jobs TAB of HP
Insight Dynamics recovery management will be empty after migration
.
Step 11: 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 FileImport/ExportImport 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’s 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.