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

ManualsBrandsHP ManualsSoftwareHP Systems Insight Manager for HP-UX

Table of Contents

Introduction

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

.........

Migration support matrix

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

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

Table 1:

Insight Software 6.1

support matrix

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

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

Table 2:

Insight Software 6.1 Os type (32/64 bit) support matrix for

above

versions in Table 1

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

Requirements

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

.......

Before you begin

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

IMPORTANT:

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

......

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: Saving Insight Orchestration and logical server files

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

Step 5: Creating space for new/target CMS system

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

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

Configuring the target CMS for migration

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

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

Step 1: Selecting 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.1 Insight Software on

the target CMS

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

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

Step 5: Launching the console on the target CMS

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

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

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

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

Exporting the source CMS configuration data

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

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

IMPORTANT:

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

....

Step 1: Backing up your CMS and database

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

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

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

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

......

Step 3: Undeploying the existing Shared Resource Domains

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

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

Step 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: Insight Software services on the source CMS version 6.1 will be stopped automatically.

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

Step 8: Running the export utility on the source CMS

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

..........

IMPORTANT:

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

....

Figure 1:

Console output of export execution

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

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

Data migration of an existing Microsoft

Windows CMS to a new Insight Software

6.1 system White Paper

Summary of content (35 pages)

PAGE 1
Data migration of an existing Microsoft Windows CMS to a new Insight Software 6.1 system White Paper Table of Contents Introduction......................................................................................................................................... 4 Migration support matrix ...................................................................................................................... 4 Table 1: Insight Software 6.1 support matrix .................................................
PAGE 2
Importing the data to the target CMS ................................................................................................... 16 Step 1: Ensuring the target CMS is prepared for an import operation ................................................... 17 Step 2: Configuring a remote database access for the import operation to the target CMS ..................... 17 Step 3: Copying saved files to the target CMS ..................................................................................
PAGE 3
PAGE 4
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. Thes e 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 5
Note: * For HP Insight Control/HP Insight Dynamics the source version of 5.3.1 maps to HP Insight Control or HP Insight Dynamics version 3.1 Table 2: Insight Software 6.
PAGE 6
Requirements  The import operation can only be performed on a CMS with Insight Software version 6.1. When performing the import operation, the Administrator must login using the same credentials that were used to install Insight Software v6.1 on the target CMS.  The same OS user names and credentials defined for use by Insight Software on the source CMS must also be defined on the target CMS.  The target CMS must have a fresh installation of Insight Software 6.1.
PAGE 7
Step 3: Saving any customer created scripts or executables The migration utility does not export or import non-HP created scripts or other executables. These files will need to be copied to the target CMS after the import operation has successfully completed. Copy the following data to a safe location that will be accessible after the import on the target CMS has been completed.  Custom scripts, executables, or other non HP Insight Software files created on the source CMS.
PAGE 8
Step 5: 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 9
Step 4: Installing version 6.1 Insight Software on the target CMS  Only the installation of Insight Software is needed; no additional discovery.  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 10
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 11
3. Count the number of scheduled tasks by selecting Tasks and LogsScheduled tasks. 4. Review the set of collections. From the left navigation pane, 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 12
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. Secure communications must be in the same state [enabled or disabled] for the CMS and all gWLM managed nodes. To unsecure communications: 1. Select SIM ConfigureID AgentsReset Communications.
PAGE 13
mxexport –f c:\export.zip –p somepassword Note: A file name with spaces is considered a valid name, e.g. “my export.zip”. A file name without *.zip will be defaulted to the *.zip extension. For example, for the file name “export” the migration utility defaults it to “export.zip”. In this example, the compressed file is saved to the root directory of the C: drive and is called export.zip. Since the password of “somepassword” was provided, future prompts for the password will not be seen. 1.
PAGE 14
recommends rerunning the export utility. Failure to do so might result with the target CMS being out of sync with the managed environment. The export operation can be executed multiple times on the source CMS, if needed. The export file is overwritten each time.
PAGE 15
ProductName : MSSW ProductVersion : 6.1 Status : Successful -----------------------------------------------------ProductName : gwlm ProductVersion : 6.0 Status : Successful -----------------------------------------------------ProductName : ApplicationDiscovery ProductVersion : 6.1 Status : Successful -----------------------------------------------------ProductName : lsm ProductVersion : 6.1 Status : Successful -----------------------------------------------------ProductName : ipm ProductVersion : 6.
PAGE 16
Status : Successful -----------------------------------------------------ProductName : vmm ProductVersion : 6.1.0 Status : Successful -----------------------------------------------------ProductName : hpsim ProductVersion : 6.1 Status : Successful -----------------------------------------------------ProductName : capacityadvisor ProductVersion : 6.1 Status : Successful -----------------------------------------------------ProductName : HPIOP2 ProductVersion : 6.1.
PAGE 17
CMS configures database connections and any other local disks and or file systems needed for the import operation. After the importation process has completed additional manual steps will need to be perfor med in order to ensure the managed environment is consistent with the imported data on the target CMS. If the new CMS has not been configured and Insight Software loaded and started on the new CMS system, perform those steps before proceeding with the following steps.
PAGE 18
3. The SQL service account must be configured to run as a domain user or administrator user that would have access to the configdata-import share named above. 4. On the target CMS, set folder permissions on the \Systems Insight Manager\data\configdata-import to full control for authenticatedUsers. 5. The temporary directory, c:\temp, must be present at the remote database server. This directory is generally provided by your Windows operation system. 6.
PAGE 19
mximport [–f] [-p pass] Where the parameters are listed in the following: -f—Optional. Used to specify a different filename or path for the export archive. The default file name is Products.zip and is placed in the \data\configdata-export directory -p—Optional. Enables the password to be passed in on the command line for non-interactive operations such as a script. This must be the same password that was used to encrypt the exported file.
PAGE 20
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. The original CMS record will be renamed to that of the target and the IP addresses will be updated.
PAGE 21
b. For SQL 2008, open Microsoft SQL Server Management Studio, select the database instance used for install, then right click and select Facets. Select 'Surface area Configuration' from the pulldown and set XPCmdShellEnabled to true. Have you followed the above Steps (y/n) ? y All HP Systems Insight Manager Plugin's Running Services will be stopped. Do you want to continue (y/n) ? y All HP Systems Insight Manager Plugin's Services Stopped Successfully WARNING! Import wipes out all data from the database.
PAGE 22
ProductVersion : 6.1 Status : Successful -----------------------------------------------------ProductName : HPIOP2 ProductVersion : 6.1.0 Status : Successful -----------------------------------------------------ProductName : ApplicationDiscovery ProductVersion : 6.1 Status : Successful -----------------------------------------------------Start Vcem postImport process. ProductName : vcem ProductVersion : 6.
PAGE 23
b. The property is “com.hp.gwlm.security.virtualLocalHostName” (host name or IP address associated with the LAN card on which to receive communications from all managed nodes. It is a global for all managed nodes). If this property is set incorrectly, then the Insight Dynamics Global Workload Manager CMS daemon fails to restart correctly. Any change is to this property must be made before any SRDs are deployed . 2.
PAGE 24
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. Verification of some key data on the target CMS can help ensure the migration was successful.
PAGE 25
Step 4: 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 26
Step 8: Running managed system setup wizard on the target CMS If the source and target systems are both version 6.1 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: MSSW which is a new feature from Insight Control v6.0 might take a while to run.
PAGE 27
Step 11: 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. Select Control PanelAdministrative ToolComputer ManagementLocal Users and GroupsGroups from the menu. 2.
PAGE 28
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 14: 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 15: Updating bookmarks 1.
PAGE 29
Insight Software components that do not support migration HP Insight Software Component Remarks 1 HP Insight Remote Support software Remote support data will need to be re-configured on the target CMS, for instance, all systems needing remote support will need to be re-imported 2 HP Version Control Repository Manager (VCRM) Uses separate migration tool. 3 HP Insight Control server deployment (RDP) Manual steps required are listed in this paper that will assist in migrating RDP jobs and scripts.
PAGE 30
Appendix A: Quiescing services on Source 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 31
Appendix B: Stop order of services Stop Order HP Insight Software Component Service Display Name 1 HP Insight Dynamics infrastructure orchestration HP Insight Orchestration 2 HP Insight Dynamics infrastructure orchestration RSCentral 3 HP Insight Dynamics infrastructure orchestration RSJRAS 4 HP Insight Dynamics infrastructure orchestration RSScheduler 5 HP Insight Dynamics configuration management HP Logical Server Automation 6 HP Insight Dynamics configuration management HP Storage Pro
PAGE 32
Xml Files to be present at [HPSIM]\config\migration Component Name Component Xml Required depended component xml’s HP Systems Insight Manager hpsim_migrate.xml HP Insight Control virtual machine management vmm_migration.xml None hpsim_migrate.xml HP Insight Control performance management PMP_Migration.xml hpsim_migrate.xml HP Insight Control power management ipm_migration.xml hpsim_migrate.xml HP Insight Managed System Setup Wizard MSSW_migration.xml hpsim_migrate.
PAGE 33
Troubleshooting Scenario 1: Out of memory error When does this happen In rare occasions CMSs with a large amount of data, you may observe an Out of Memory error. Solution Edit the mxexport.bat/mximport.bat file to increase the memory allocated to the export processes. In the Systems Insight Manager installation bin directory, for example C:\program files\HP\Systems Insight Manager\bin, edit mxexport.bat with any text editor change the line that starts with java and add –Xmx1024m or larger value.
PAGE 34
1. Open the template in edit mode 2. Select the first entry in the drop down list for Arch 3. Save it. Scenario 4: The export or import includes all products, only wanted HP SIM data. When does this happen By default the data migration tool will export installed products using a set of XML configuration files. The same applies to the import, on import both the export file and the set of installed components is examined to pull the common set of data from the exported file.
PAGE 35
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 Virtualization Manager Software with Logical Server Management: User Guide. This and other ID docs are available at www.hp.com/go/insightdynamics/docs .