paper Technical white paper Data Migration of an Existing Microsoft Windows CMS to a New Insight Management 7.3 System HP Insight Management 7.
Table of Contents Introduction ....................................................................................................................................................... 4 Migration support matrix ................................................................................................................................... 4 Migration support matrix for IPv4/IPv6 CMS ......................................................................................................
Technical White Paper | HP Insight Management 7.3 Appendix D: Partner services tool.................................................................................................................... 59 Partner service CLI usage................................................................................................................................. 59 Appendix E: Migration of CMS users in different scenarios ..............................................................................
Introduction The Insight Management data migration tools (DMT) provide an easy mechanism to migrate an existing Insight Management central management server (CMS) from one system 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.
Technical White Paper | HP Insight Management 7.3 Note: For HP Insight Control and HP Matrix OE, the source version of 5.3.1 maps to HP Insight Control or HP Matrix OE version 3.1. From 6.3, the migration utility supports using the source CMS’s hostname/ IP address for the target CMS, whether the source/target CMSs are the same system or different systems. However, HP recommends using a different system for the target CMS.
Migration support matrix for workgroup/domain Table 3. Insight Management 7.3 DMT support for workgroup/domain Source CMS System Target CMS System Supported In Domain X In Domain X Yes In Domain X In Domain Y No In Workgroup In Domain Yes In Domain In Workgroup No In Workgroup X In Workgroup X Yes In Workgroup X In Workgroup Y No Note: X and Y are names of different domains and workgroups.
Technical White Paper | HP Insight Management 7.3 • Microsoft SQL Server 2012 Business Intelligence SP1 • Microsoft SQL Server 2012 Web (Support only for HPSIM) Note: Data migration is not supported for Oracle databases. All Windows operating systems supported by Insight Management are fully supported in data migration. For supported operating systems, go to http://www.hp.com/go/insightsoftware/docs. Note: Data migration is not supported for Linux or HP-UX CMS operating systems.
Migration scenario Source CMS Target CMS Cluster IC/IDVSE with SQL DB in same cluster Cluster IC/IDVSE with remote SQL DB Same domain Workgroup to domain Different domain Yes No No Table 8. Insight Management 7.
Technical White Paper | HP Insight Management 7.3 Table 9. Insight Management 7.
HP Matrix infrastructure orchestration (IO) support matrix Starting in 6.3, federated CMS is enabled by default in every new installation. Even if a single CMS is installed and configured, federation may be enabled. Thus, when planning the migration of IO data, make sure to review Table 10 carefully. In order to check whether federated CMS is enabled in your environment: • In CMS, open the hpio.properties file located at \conf and search for the federated.io property.
Technical White Paper | HP Insight Management 7.3 • hpio.build • hpio.version • keystore.file.path • matrix.cloud.connecter.enabled • oo.admin.username • oo.disk.scrubbing.path • oo.global.service.end.action.path • oo.manual.storage.zoning.path • oo.network.provisioning.path • oo.os.deployment.path • oo.service.action.subdirectories • oo.service.approval.action.path • oo.service.lease.notification.path • oo.service.recovery.path • oo.service.ws.path • oo.storage.allocation.
• vmm.cluster.refresh • volume.exclusion.list Settings in the dr.properties file are not automatically migrated from the source to the target CMS. If any settings in dr.properties have been changed, make a backup copy of the file before the migration and copy it to the target CMS after the migration is complete. Migration of Operations Orchestration repositories HP Operations Orchestration local repositories are migrated from the source CMS to the target CMS with no extra steps required.
Technical White Paper | HP Insight Management 7.3 • The target CMS is the same physical system as the source CMS when the target CMS is a cluster CMS. • Importing into the target CMS in a workgroup (for example, x) from the remote SQL server in the workgroup (for example, y) is not supported. Table 11. Insight Management components that do not support migration HP Insight Management component Notes HP Insight Remote Support software Remote support data must be reconfigured on the target CMS.
Step 2: Collecting OS level user names and passwords from old CMS The same OS user names and credentials defined for use by Insight Management on the source CMS must also be defined on the target CMS. If domain accounts are used, ensure the target system has joined the same Windows domain as source. Step 3: Saving any customer created scripts or executable The migration utility does not export or import non-HP created scripts or other executable.
Technical White Paper | HP Insight Management 7.3 Configuring the target CMS for migration To avoid data loss in the target CMS, perform the steps defined in the Exporting the source CMS configuration data section on the target CMS before proceeding with configuring the target CMS for migration. If the source CMS uses a remote database, then the data from the remote database is extracted as part of the export process.
• If the same remote database server is to be used, either a new instance must be configured or the old database must be dropped for Insight Management to install. • Follow the instructions in the Insight Management Installation and Configuration Guide, Chapter 2, to install the same software products that exist on the source CMS. The configuration guide can be found at http://www.hp.com/go/insightsoftware/docs.
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.
4. Copy the exported job file and any customized script files to a safe location. 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 6: Unsecuring communications on the CMS when Matrix OE Global Workload Manager (gWLM) is in use This step can be omitted if the CMS is not being used to manage gWLM nodes.
Technical White Paper | HP Insight Management 7.3 privileges, and should be the same user that installed the Insight Management on the source CMS. Note: If HP Infrastructure Orchestration uses a remote HP OO server, then modify the export utility configuration to avoid HP OO migration. Perform the following steps: 1. In the source CMS, open Windows Explorer. 2. Navigate to \config\migration location. 3. Remove the HPIOP2.xml file from the \config\migration directory.
3. In the command prompt window, execute the export command: mxexport 4. A prompt for a data encryption password appears. Type the password and press the Enter key. The password does not appear in clear text. 5. A dialog appears stating All HP Insight Management running services will be stopped. Do you want to continue? Type Y and press the Enter key to proceed for migration. If you type N and press the Enter key, the migration is aborted.
Technical White Paper | HP Insight Management 7.3 All HP Insight Management running services will be stopped. Do you want to continue (y/n) ? y All HP Insight Management services stopped successfully. Starting data export. Product Name : HP Insight managed system setup wizard Product Version : 7.
---------------------------------------------------------Time taken by HP Matrix OE Capacity Advisor to export: 0 Min, 44 Sec Product Name : HP Insight Control power management Product Version : 7.3 Status : Successful ---------------------------------------------------------Time taken by HP Insight Control power management to export: 0 Min, 29 Sec Product Name : HP Matrix OE infrastructure orchestration [HP Matrix OE infrastructure orchestration] Product Version : 7.3.
Technical White Paper | HP Insight Management 7.3 Time taken by HP Insight Control virtual machine management to export: 0 Min, 49 Sec Product Name : HP Insight Control performance management Product Version : 7.3.0 Status : Successful ---------------------------------------------------------Time taken by HP Insight Control performance management to export: 0 Min, 56 Sec Product Name : HP Systems Insight Manager Product Version : 7.
Time taken by HP Operations Orchestration software to export: 0 Min, 45 Sec Export operation completed in: 12 Min, 38 Sec Successfully EXPORTED data to file: C:\Program Files\HP\Systems Insight Manager\data\configdata-export\Products.zip. Product Status xml is available in: C:\Program Files\HP\Systems Insight Manager\logs\DMTStatus.xml C :\> Importing the data to the target CMS The import utility checks for installed software dependencies and imports the data in a predefined order.
Technical White Paper | HP Insight Management 7.3 Note: In case the target CMS is a cluster CMS with a remote database, then the export zip file should be placed in a custom folder (for example, C:\dmt) on the local drive of the target CMS server instead of configdata-import. For example, in the local C: drive, create a folder named dmt and place the export.zip in it C:\dmt\export.zip. If you want to manually transfer files to remote SQL server the following steps must be followed, 1.
export file is placed in a custom folder (for example, C:\dmt), the location can be specified on the command line when the import operation is done. 2. Copy the saved scripts and/or custom executables from the safe location, which has been saved during Step 3: Saving any customer created scripts or executables in the Before you begin section to the target CMS in the appropriate location. 3.
Technical White Paper | HP Insight Management 7.3 10. After the certificate has been successfully downloaded, execute certutil [ie hpcloud.cer] Example: c:\>certutil hpcloud.cer ... Subject: CN=hpcloud.com OU=HPCS O=Hewlett-Packard L=Seattle S=Washington C=US 11. Copy the CN value [ie hpcloud.com] and paste the value in the \config\migration\cloudcertificatequalifier.props file. Example: cloudqualifier=hpcloud.
The parameters are as follows: -f—Optional. Specifies a different filename or path for the export archive. The default file name is Products.zip and is placed in the \data\configdataimport directory on the source CMS. -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. If –p is not specified, the user is prompted to enter the password.
Technical White Paper | HP Insight Management 7.3 For example, mximport -f c:\export.zip -p somepassword -v {IP address} -n clustersite.ha.com -h hpsim_virtual_network_name_source.ha.com -t hpsim_virtual_network_name_target.ha.com Cluster CMS with remote database example mximport –f –p –v -n -r -h -t For example, mximport –f c:\export.
7. A dialog appears Extracting the zip file . 8. If the database is remote a dialog appears Do you want to manually transfer database files to remote DB server for security (y/n) ?: type Y/N and press enter ,you are prompted to confirm whether the prerequisite configuration steps have been followed for remote database access. Type Y if you have performed the steps, or type N if you have not performed the steps.
Technical White Paper | HP Insight Management 7.3 Do you want to proceed (y/n)?: y All HP Insight Management services stopped successfully. ---------------------------------------------------------Extracting the zip file C:\Program Files\HP\Systems Insight Manager\data\configdata-import\Products.zip Do you want to manually transfer database files to remote DB server for security (y/n) ?: N The following steps are needed to perform only if the target CMS is configured with a remote SQL server database. 1.
Product Version : 7.3 Status : Successful ---------------------------------------------------------Time taken by HP Insight managed system setup wizard to import: 0 Min, 2 Sec Product Name OE] : HP Insight Global Workload Manager [HP Matrix Product Version : 7.
Technical White Paper | HP Insight Management 7.3 ---------------------------------------------------------Time taken by HP Matrix recovery management to import: 0 Min, 18 Sec Product Name : HP Matrix infrastructure chargeback [HP Matrix infrastructure orchestration] Product Version : 7.3.
---------------------------------------------------------Product Name : HP Matrix OE infrastructure orchestration [HP Matrix OE infrastructure orchestration] Product Version : 7.3.0 Status : Successful ---------------------------------------------------------Time taken by HP Matrix infrastructure orchestration to import: 0 Min, 27 Sec Product Name : HP Insight Control virtual machine management Product Version : 7.3.
Technical White Paper | HP Insight Management 7.3 2. Navigate to \conf 3. Open the hpio.properties file and make sure the following lines contain the correct values. oo.host=. oo.port= oo.username= If the target CMS is a cluster CMS, use Failover Cluster Manager to bring the Insight Management cluster application online.
Start order HP Insight Management component Service display name 11 HP Matrix OE configuration management HP Extensible Storage & Server Adapter 12 HP Matrix OE configuration management HP Storage Provisioning Manager Service 13 HP Matrix OE configuration management HP Logical Server Automation 14 HP Matrix OE infrastructure orchestration HP Matrix Infrastructure Orchestration 15 HP Matrix infrastructure chargeback HP Matrix infrastructure chargeback Post import operation tasks Step 1: Ver
Technical White Paper | HP Insight Management 7.3 • Click [Prev] to return to the previous page. 6. Click [Done]. View the task results by selecting the desired Data Collection task on the All Scheduled Tasks page. Step 3: Verifying SMTP settings on the target CMS After a migration to a new host, it is possible that the SMTP configurations might need to be updated. Log into the CMS console, select OptionsEventsAutomatic Event HandlingE-mail settings, and then verify that the SMTP server is correct.
iv. Verify the port number and adjust as needed. v. Click OK. b. If WMI Mapper was installed by the Insight Management Installer on the target cluster, then follow the steps to configure the WMI Mapper proxy. i. Check the box to select the current host and click Delete. ii. Click New. iii. Enter the FQDN of the Systems Insight Manager virtual server name in the target cluster. iv. Verify the port number and adjust as needed. v. Click OK.
Technical White Paper | HP Insight Management 7.3 ii. Change the system name/IP field to contain the FQDN of the target cluster Systems Insight Manager virtual server name. iii. Click the Credentials… button. iv. The Sign-in tab is selected. Under Use these credentials ensure that the credentials are set to the service account credentials you provided to the Insight Management Installer on the target CMS, for example, domain\username and password. v. Clear the If these credentials fail box. vi. Click OK.
b. Verify that the System Name column includes entries for both the Failover Cluster virtual server and the Systems Insight Manager virtual server. They may be represented either by their virtual server name or IP address. i. The Server Type of the Failover Cluster virtual server is Cluster. ii. The Server Type of the Systems Insight Manager virtual server is Server. c.
Technical White Paper | HP Insight Management 7.3 vii. The Sign-in tab is selected. Under Use these credentials enter the service account credentials you provided to the Insight Management Installer on the target CMS, for example, domain\username and password. viii. Clear the If these credentials fail box. ix. Click OK. x. Click Save to complete. 12. Run the updated discovery task. a. In the discovery task list box, select Discover physical cluster nodes. b. Click Run Now. c. Wait for the task to complete.
SPM_HOST= 16. In the left pane, click All Systems. You can find the cluster virtual server name, the Systems Insight Manager virtual server name, and the cluster nodes in All Systems. Figure 3 is an example of the display. Your configuration might contain additional systems. Figure 3: Two mode ProLiant cluster after Systems Insight Manager discovery 17. Click the virtual server name of the Failover Cluster. In Figure 3, it is cms-c2-cluster. The Cluster Monitor appears.
Technical White Paper | HP Insight Management 7.3 19. HP SIM Group resources are now owned by the secondary node. Repeat step 18 to move the HP SIM Group resources back to the primary node, and then verify the move. Follow the steps in the “Final configuration steps” section of Installing and Upgrading HP Insight Management 7.3 on Windows Server 2012 Failover Clusters.
Note: VCEM automatically locks to the target CMS after migration. If VCEM is to be uninstalled on the source CMS, first edit the registry on the source CMS. Locate the key HKEY_LOCAL_MACHINESOFTWAREHewlett-PackardVirtual Connect Enterprise ManagerSettings, and set checkVCDomain to false. Step 9: Redeploying Shared Resource Domains when using Matrix OE Global Workload Manager Users of Matrix OE Global Workload Manager must perform several additional steps.
Technical White Paper | HP Insight Management 7.3 a. Navigate to the HP Matrix Recovery Storage Management Servers tab. b. Select 3PAR Storage Management Server, and click Edit. c. Click Save without changing any data. 4. Perform a rehearsed failover. For validation of the migration, HP recommends performing a planned failover as outlined in Chapter 8 of the Matrix OE Recovery Management User Guide.
Note: When selectively migrating, ensure the components selected for migration are installed in the target CMS. Step 14: Acquiring a new CA certificate for the target CMS If the source CMS had a CA-signed certificate, and if the source CMS/target CMS are two different servers with different names/IP addresses, then request a new CA certificate from a certificate authority (CA). Steps to acquire a new CA certificate and import: 1. Go to option>>security>>HP Systems Insight Manager Certificate. 2.
Technical White Paper | HP Insight Management 7.3 12. Click on more in third line 13. Browse the file which you have downloaded from “Download certificate” link. 14. Click on import. Step 15: If this is a secondary CMS migration, perform the following operations 1. Log in to the primary CMS in the federation that the migrated secondary CMS is part of. 2. Stop the HP Matrix infrastructure orchestration windows service. 3. Remove the source CMS from the federated CMS list using SIM Federated Configuration.
mxnodesecurity –a –p dsc_sas –c username:password -t on -n VMware Auto Deploy (AD) mxnodesecurity –a –p dsc_custom –c username:password -t on -n ipaddress of VMware AD server Step 18: Importing an SSL certificate for access to a cloud provider 1. Copy \conf\savvis-cloud-pools.xml to the target CMS. 2. Find all of the Id values in savvis-cloud-pools.xml, and copy the \conf\.properties files to the target CMS. 3.
Technical White Paper | HP Insight Management 7.3 FAQs 1. How do I migrate data from HP Insight Software 5.3.1 to HP Insight Management 7.3? Answer: Before the migration process begins, the source CMS must be upgraded to HP Insight Management 7.3. For more details about the upgrade process, see Step 5: Upgrading to version 7.3. 2. How do I selectively migrate components to a target CMS machine from a source 7.
Component name HP Application Discovery XML files required in \config\migration Component XML file Required dependent component XML files ApplicationDiscovery.xml gwlmmigration.xml hpsim_migrate.xml HPIO.xml hpsim_migrate.xml vmm_migration.xml HP Infrastructure Orchestration software vcem_migration.xml HPIOP2.xml lsmmigration.xml Chargeback.xml HPIO.
Technical White Paper | HP Insight Management 7.3 Where MAX_GET_CONNECTION_RETRIES = maximum number of attempts to get a valid database connection. The current default value is 10. SLEEP_TIME_BETWEEN_RETRIES = maximum amount of time to wait between attempts. In other words, the program randomly waits from 0 to SLEEP_TIME_BETWEEN_RETRIES milliseconds. The current default time is 10000 milliseconds.
3. Ensure all the steps are followed as specified at Step 2: Configuring remote database access for the import operation to the target CMS. Scenario 6: Power Management data not exported To minimize any power consumption history loss after migration, ensure that you have completed a full power-data collection for all systems immediately prior to the migration. Power data collection can be initiated using the Refresh Data option on the Power/Thermal data reports page for a selected group of systems.
Technical White Paper | HP Insight Management 7.3 Sep 16, 2010 18:30:58 colt11b.fc.hp.com: SEVERE [10] Error starting CMS daemon: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.AccessException: Registry.Registry.rebind disallowed; origin /15.146.233.1 is non-local host. Make sure C:\Program Files\HP\Virtual Server Environmentvseinitconfig has been run after gWLM installation or upgrade. Solution In multi homed networks, ensure gWLM property com.hp.gwlm.
Task for Logical Server logical-server-name has failed. Logical server job completed with a failure status. Failure: Deployment server credentials not found.
Technical White Paper | HP Insight Management 7.3 Scenario 11: After data migration, the server pools are empty (all managed nodes appear in Unassigned pool) Verify whether the server pools are empty after the import process. Move the managed nodes to the server pools if the managed nodes differ from the source or if they are available only in the unassigned pool.
5) Type Matrix_Administrator, Matrix_Architect, or Matrix_Designer, corresponding to the role you are editing into the search term field. 6) Click Search. 7) Select the corresponding group for the CMS. 8) Click OK. 9) Select the row of the table containing an SSID. 10) Click Remove. In addition, if there are any custom local users or groups in the original CMS that were used with SPM, you will see additional SSIDS in one or more roles.
Technical White Paper | HP Insight Management 7.3 Logs menu in HP SIM. Click the End Time column name to sort the task list. Tasks displaying an empty End Time have not completed. 6. Ensure all in-progress installation and configuration tasks have completed (for example, Configure and Repair Agents tasks or Deploy Drivers, Firmware or Agents). You can view the status of the tasks by selecting View Task Results… from the Tasks & Logs menu in HP SIM. Click the End Time column name to sort the task list.
mxexport [–f ] [-p ] Where the parameters are listed in the following: -f—Optional. Specifies a different filename or path for the export archive. The default file name is Products.zip and is placed in the \data\configdataexport directory -p—Optional. Enables the password to be passed in on the command line for non-interactive operations such as a script. This is the password that will be used to encrypt the exported file, Products.zip.
Technical White Paper | HP Insight Management 7.3 mximport –f –p –v -n -r -h -t For more details, see Step 5: Upgrading to version 7.3. Appendix D: Partner services tool The partner service tool is a batch script located in the Systems Insight Manager installation directory.
Before migration group-todomain Installed CMS user Workgr oup/us erX CMS user CMS user After migration Installed CMS user domainna me/userY Installed CMS user domainna me/userY Source Installed user is changed to target installed user Workgr oup/us erX1 CMS user domainna me/userX1 Migrated from source by adding domainnam e instead of workgroup Workgr oup/us erX2 CMS user domainna me/userX2 Migrated from source by adding domainnam e instead of workgroup CMS user domainna me/userY1 These u
Technical White Paper | HP Insight Management 7.
Appendix G: Running the fix_fqdn_dmt.pl script This script updates existing values in the primary CMS database to be consistent with the current secondary CMS FQDN. Use this script to fix the FQDN on secondary CMSs only, because the primary CMS FQDN is automatically handled by the migration process. Before running the script, make sure Perl and Microsoft SQL Server SQLCMD are installed on the primary CMS.
Technical White Paper | HP Insight Management 7.3 INPUT_FILE - Path for the input file. An input file provided containing FQDN pairs , . SERVER - Database server. The hostname or IP address of the remote database. PORT - Database server port number. The database server port. Default value is 1433. INSTANCE - Database instance. The database instance name containing the IO database. USERNAME - Database username. User name for the remote database. PASSWORD - Database password.
For more information See the Matrix OE troubleshooting guides at www.hp.com/go/insightdynamics/docs. See the Backing up and restoring HP Insight Management v7.3 Central Management System (Windows) white paper at www.hp.com/go/insightsoftware/docs. See the LSM troubleshooting information included in the HP Matrix Operating Environment Logical Server Management User Guide. This and other Matrix OE manuals are available at www.hp.com/go/matrixoe/docs. Sign up for updates hp.
