HP Insight Management 7.3 DMT White Paper

Technical White Paper | HP Insight Management 7.3

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

2. See Appendix A: Quiescing services on the source CMS to validate service information.

Step 2: If using Matrix OE recovery management, perform the following operation

The Matrix OE recovery management's hp_ir.properties file contains the user-definable property

values. The file is located at 'conf' directory under Matrix Recovery Management installed

directory. An example full-path of the file is C:\Program Files\HP\Insight

Recovery\conf\hp_ir.properties. If you had any property value changes in this file, you have to

make a backup (copy) of this file for later on post-import operation.

Step 3: 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 the command-line interfaces to validate nodes. For instance, you can export node lists with mxnode –

lf > nodelist.xml and save it. For more information see the following support manual:

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

Step 4: Undeploying the existing Shared Resource Domains

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

Step 5: Reconfiguring Insight Control server deployment agents

This is not applicable to a 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 the servers from the server deployment console.

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

3. If the source CMS host name and IP address is not reused, then enter the IP address of

the target CMS so 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