Data migration of an existing MS Windows CMS to a new Insight Software 6.0 system

ManualsBrandsHP ManualsSoftwareHP Systems Insight Manager 5.x Linux Software

Table of Contents

Introduction

................................

.........

Migration support matrix

................................

......................

Requi

rements

................................

.......

Before you begin

................................

Step 1: Choosing the appropriate time for CMS migration

................................

....

Step 2: Collecting OS level user names and passwords from old CMS

................................

...................

Step 3: Saving any customer created scripts or executables

................................

Step 4: Creating space for new/target CMS system

................................

.............

Configuring the target CMS for migration

................................

...............................

Step 1: Se

lecting new host name and IP address for a new system as the target CMS

..............................

Step 2: (Optional) Upgrading memory and firmware on the target CMS system

................................

......

Step 3: Installing and pre

configuring the target CMS

................................

...........

Step 4: Installing version 6.0 Insight Software on the target CMS

................................

..........................

Step 5: Launching the console on the target CMS

................................

................

Step 6: Upgrading to version 6.0 or installing migration software on the source CMS

..............................

Exporting the source CMS configuration data

................................

.........................

Step 1: Backing up your CMS and database

................................

.......................

Step 2: (Opti

onal) Recording key data items to be used for import verification

................................

........

Step 3: Undeploying the existing Shared Resource Domains

................................

tep 4: Reconfiguring Insight Control server deployment agents

................................

.............................

Step 5: Un

securing communications on the CMS when Insight Dynamics Global Workload Manager (gWLM)

is in use

................................

........

Step 6: Quiescing running services on the source CMS

................................

......

Step 7: Stopping Insight S

oftware services on the source CMS

................................

............................

Step 8: Configure the mxexport batch file for larger CMS installs

................................

.........................

Step 9: Running the export utility on the source CMS

................................

..........

Importing the data to the target CMS

................................

...

Step 1: Ensuring the target CMS is prepared for an import operation

................................

...................

Step 2: Copying saved files to the target CMS

................................

..................

Step 3: Stopping services on the target CMS

................................

.....................

Step 4: Confi

guring a remote database access for the import operation to the target CMS

.....................

Step 5: Configure the mximport batch file for larger CMS installs

................................

........................

Step 6: Running the import utility on the target CMS

................................

...........

Step 7: Configure Insight Dynamics Global Workload Manager property file

................................

......

Step 8: Restarting the Insight S

oftware services on the target CMS

................................

.......................

Data migration of an existing Microsoft

Windows CMS to a new Insight Software

6.0 system White Paper

Summary of content (28 pages)

PAGE 1
Data migration of an existing Microsoft Windows CMS to a new Insight Software 6.0 system White Paper Table of Contents Introduction......................................................................................................................................... 3 Migration support matrix ...................................................................................................................... 3 Requirements..................................................................................
PAGE 2
Post import operation tasks ................................................................................................................. 19 Step 1: Verifying the import on the target CMS.................................................................................. 19 Step 2: Verifying SMTP settings on the target CMS ............................................................................ 19 Step 3: Re-entering vCenter credentials on the target CMS ...............................................
PAGE 3
Introduction The Insight Software data migration tools (DMT) provide an easy mechanism to migrate an existing Insight Software central management server (CMS) from one hosted environment to another. These tools are designed to relocate a CMS to a new hosted environment when there is a need to change the underlying hardware or operating system of the CMS, without losing any of the customized data located on the CMS.
PAGE 4
6.
PAGE 5
Before you begin The data migration process enables the target CMS to be hosted on a new system in the infrastructure or on the existing system after an OS upgrade. In either instance, critical OS-level information must be configured on the target CMS. HP recommends for the target CMS to be hosted on a different system.
PAGE 6
Step 4: Creating space for new/target CMS system  Ensure at least 20GB free disk space exists for the export file on both the source and target CMS if Insight Dynamics is installed. The file size might vary, depending on the number of discovered systems and on the Insight Software products that are installed. The file can be much smaller, 50MB, if just HP SIM is installed with several hundred systems.
PAGE 7
Step 4: Installing version 6.0 Insight Software on the target CMS Only the installation of Insight Software is needed; no additional discovery, etc.   If the same remote database server is to be used, either a new instance must be configured or the old databases must be dropped for Insight Software to install.  Follow the instructions in the Insight Software Installation and Configuration Guide, chapter 2, to install the software products of your choosing.
PAGE 8
Option 2: Download the migration.exe file from the following ftp location ftp://hp.com/pub/softlib2/software1/pubsw-windows/p197989050/v60563 . Create a folder on the Source CMS called migration here: c:\Program Files\HP\Systems Insight Manager\migration. Copy this file to the c:\Program Files\HP\Systems Insight Manager\migration folder. Note: OS administrative privileges are required for the signed in user on the source CMS. 3. On the source CMS, run the migration.
PAGE 9
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: Command line interfaces are a good way to validate nodes. For instance, you can export node lists with mxnode –lf and save it off to compare post migration.
PAGE 10
Note: The deployment job history for managed computers cannot be migrated. Be sure to select the desired operating systems when installing server deployment on your target CMS. Step 5: Un-securing communications on the CMS when Insight Dynamics Global Workload Manager (gWLM) is in use This step may be skipped if you are not using the CMS to manage gWLM nodes. If secure communications are in use, please unsecure communications on the CMS and all managed nodes.
PAGE 11
13 HP Insight Dynamics – VSE Workload Management for HP Integrity servers HP Global Workload Manager Central Management Server 14 HP Insight Control server migration HP Insight Control server migration Application Service 15 HP Insight Control server migration HP Insight Control server migration Web Service *These services are not present in IS 3.1 Step 8: Configure the mxexport batch file for larger CMS installs Edit the mxexport.bat file to increase the memory allocated to the export processes.
PAGE 12
a.Navigate to Start menuRun. b.Type cmd, and then click OK. The command prompt window appears. In the command prompt window, execute the export command: mxexport You will be prompted to enter the password. The password will not be displayed in clear text in this case, enter the password when prompted. IMPORTANT: Be sure to retain the password, because it must be provided during the import operation. Note: A customized location can be provided to store the exported data. See the export parameter table.
PAGE 13
Figure 1: Example export execution Importing the data to the target CMS The import utility checks for installed software dependencies and imports the data in a predefined order. As part of the import operation, some data from the export operation is replaced with data to match the target system, such as the CMS name and IP address. This enables a migration to a new CMS with a different host name and IP address. Other environmental changes might occur for the CMS, such as a local or remote database.
PAGE 14
2. 3. Ensure the steps in the “Configuring the target CMS for migration” section have been performed. Ensure the steps in the Exporting the source CMS configuration data have been performed. Step 2: Copying saved files to the target CMS 1. Copy the zip file created during the export operation on the source CMS to the target CMS folder located at \data\configdata-import.
PAGE 15
HP Insight Control server migration HP Insight Control server migration Web Service *These services are not present in Insight Software 3.1 Step 4: Configuring a remote database access for the import operation to the target CMS The following steps must be performed only if the target CMS is configured with a remote SQL server database.
PAGE 16
Insight Manager\bin, edit mximport.bat with any text editor change the line that starts with java and add –Xmx512m. For example the line should look like the following. java -Xmx1024m -Dora.home=%ORA_HOME% -cp %MYPT% com.hp.mx.migration.cli.CLIWrapper mximport %* Step 6: Running the import utility on the target CMS The import utility is a command-line interface (CLI) command that must be run from a standard command prompt on a Windows operating system.
PAGE 17
A warning message will be displayed indicating that the import will wipe out all data from the database. 4. Press Y to the import process, or press N to terminate the import process. Note: The import process will clear the data on the target system and database before it actually imports any data into the target CMS. Note: If the target CMS had been previously discovered by the source CMS that record will be removed, and the original CMS record will remain intact.
PAGE 18
Figure 2: Example import tool operation Step 7: Configure Insight Dynamics Global Workload Manager property file This step may be skipped if you are not using the CMS to manage gWLM. Users of Insight Dynamics Global Workload Manager must perform several additional steps. For complete information, see the Insight Dynamics Global Workload Manager 6.0 Users Guide. 1. Verify the following property in the Insight Dynamics Global Workload Manager agent property file. a.
PAGE 19
Step 8: Restarting the Insight Software services on the target CMS Start the services listed in Table 2 in the reverse order in which they were stopped. Note: The “HP Application Discovery “service has to restarted on source and target systems after installation Post import operation tasks Step 1: Verifying the import on the target CMS HP recommends logging in to the target (new) CMS to verify the data has successfully migrated.
PAGE 20
Step 3: Re-entering vCenter credentials on the target CMS For Insight Control virtual machine management, if the source CMS version is less than 6.0, then the vCenter Server credentials must be re-entered. To enter the vCenter Server credentials, log into the CMS console, select OptionsVMware vCenter Settings. Each of the ESX hosts must be present in only one vCenter Server. The credentials of all the vCenter Servers must be entered to continue managing the ESX hosts.
PAGE 21
Step 7: Running managed system setup wizard on the target CMS If the source and target systems are both version 6.0 of the Insight Control or Insight Dynamics software bundle including Manage System Setup Wizard (MSSW), create a new task, and then run Manage System Setup against all systems. Note: The MSSW a new feature in Insight Control v6.0, might take a while to run.
PAGE 22
Step 10: Migrating the Insight Dynamics orchestration users to the corresponding user groups on the target CMS when using Insight Dynamics orchestration With the user names and passwords collected before the import operation, create the users on the target CMS (For domain users, this step is not required.) Associate the users with the corresponding Windows User Groups required by HP IO: 1. Go to Control PanelAdministrative ToolComputer ManagementLocal Users and GroupsGroups. 2.
PAGE 23
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 6.0 Installation and Configuration Guide for Microsoft Windows. Step 14: Updating bookmarks 1. 2.
PAGE 24
Appendix A: Quiescing services for a pre v6.0 CMS Prior to stopping the HP Insight Software services and backing up your environment, you must quiesce Insight Software components. The following actions only need to be performed for components that are installed and currently in use in your environment. Note: The steps might vary slightly depending on the version of software installed on your system. See the product documentation for your release for additional information. 1.
PAGE 25
IMPORTANT: If, in your environment, you have customized an application, workflow or script to asynchronously issue Insight Software requests, you must temporarily disable this functionality to avoid generating Insight Software requests during the upgrade process.
PAGE 26
Troubleshooting Scenario 1: Where some or all services are running c:\mxexport .... .... WARNING! Service is running for the following plug-ins: APPLICATIONDISCOVERY, CA PACITYADVISOR, GWLM, HPIO, HPSIM, VMM. Please stop all services and restart the export function.. 14 Dec 2009 19:15:03,344 INFO [HPSIM_DEBUG] Services are running for the follow ing plug-ins APPLICATIONDISCOVERY, CAPACITYADVISOR, GWLM, HPIO, HPSIM, VMM. Please stop all plug-in services and restart the migration function.
PAGE 27
Scenario 4: In Application Discovery the results of template is not the same on the target CMS as was on the source CMS. When does this happen Templates on source CMS are defined to use a wild card (Any) for any of the System Scope fields (Arch, OSver, OS type). Solution When the user perform DMT of AD and when the template does not provide the desired results the following needs to be performed for all System Scope (Arch, OSver, OS type) templates. 1. Open the template in edit mode 2.
PAGE 28
For more information Insight Dynamics troubleshooting guides at www.hp.com/go/insightdynamics/docs Backing up and restoring HP Insight Software v6.00 Central Management System (Windows ) white paper at www.hp.com/go/insightsoftware/docs. LSM troubleshooting information is included in HP Insight Manager 6.0 Software with Logical Server Management: User Guide. This and other ID docs are available at www.hp.