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

Note:

If import cannot be completed and the source CMS must be used again, steps 2,

3, and 4 must be undone. See steps 9 and 12 in the post import operations section.

Step 1: Backing up your CMS and database

This step only applies when the target CMS is the same system as the source CMS.

HP recommends making a new system separate from the source CMS available for the import. However, if

the hardware used for the target CMS is the same as the source CMS, you must back up your CMS and

database as a precaution. If an unexpected error occurs, the CMS and database can easily be restored from the

backup taken.

Before running an export operation, complete the following:

1. Make a full system backup of the source CMS and, if applicable, the remote database.

2. Refer to Appendix A to validate service information.

Step 2: Optional: Recording key data items to be used for import verification

1. View the All Systems system list, and record the total number of systems.

2. Obtain the number of users. Go to OptionsSecurityUsers and Authorizations.

3. Count the number of scheduled tasks. Go to Tasks and LogsScheduled tasks.

4. Review the set of collections. Go to the left navigation pane, and select Customize to view all

collections and the details.

Note:

You can use command-line interfaces to validate nodes. For instance, you can

export node lists with mxnode –lf and save it. For more information please

refer the following support manual.

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01651227/c01651

227.pdf

Step 3: Un-deploying the existing Shared Resource Domains

The required migration pre-export action for gWLM is to un-deploy all Shared Resource Domains.

Step 4: Reconfiguring Insight Control server deployment agents

This is not applicable to Cluster CMS.

Before shutting down the source CMS, the deployment agents must be reconfigured to interact with the target

CMS. To reconfigure the agents:

1. On the source CMS, select servers from the server deployment console.

2. Right-click and select Change Agent SettingsProduction Agent.

3. If the source CMS’s host name and IP address is not reused, then Enter the IP address of the target

CMS so that agents can connect to the target CMS.

As the deployment agents on the servers selected previously connect the target CMS, those servers are added

to the deployment console.

If customized deployment jobs exist on the source CMS, then you must export the jobs from the source CMS

for later importing to the target CMS.

To export custom jobs on the source CMS: