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

12
Step 1: Backi
ng 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 sa
me 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
be restored.
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.
Sept 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

S
ecurity

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 c
ommand
-
line interfaces to validate nodes. For instance, you
can export node lists with
mxnode
–
lf
and save it.
Step 3: Un
-
deploying the existing Shared Resource Domains
You must u
n
-
deploy the exi
sting Shared Resource Domains is required migration pre
-
export actions for
gWLM.
Un
-
deploy all Shared Resource Domains.
Step 4: Reconfiguring Insight Control server deployment agents
This is n
ot applicable to Cluster CMS.
Before shutting down the source CM
S,
t he 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.
Enter the IP add
ress 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 CM
S,
then
you must export the jobs from the source
CMS for later import
ing
to the target CMS.