HP Insight Control Server Migration 7.0 User Guide Abstract HP Insight Control server migration provides an automated, accurate and affordable way to migrate existing servers to the latest ProLiant server technologies or the latest virtualization platforms. This guide explains processes and procedures that are not appropriate for the product's online help. The information in this guide is intended for users with network administrator-level access and knowledge.
© Copyright 2012 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents I Overview and concepts................................................................................9 1 Server migration introduction..................................................................10 Overview..........................................................................................................................10 Installing and configuring server migration software...............................................................
7 Preparing the destination server and deploying the destination agent..........28 Prerequisites......................................................................................................................28 Physical destination servers.............................................................................................28 Virtual machine hosts.....................................................................................................28 Linux destination size requirement............
Cause.....................................................................................................................46 Suggest action.........................................................................................................46 Launching server migration from Systems Insight Manager throws an exception.....................46 Cause.....................................................................................................................46 Suggested action.........................
Suggested action......................................................................................................52 Supported storage controllers display Unknown on the Boot CD ISO....................................52 Cause.....................................................................................................................52 Suggested action......................................................................................................
Suggested action......................................................................................................58 Unrecoverable sector-read errors on the source server hard drive are not supported and fail a Windows P2P or P2V migration...................................................................................58 Cause.....................................................................................................................58 Suggested action..........................................
Cause.....................................................................................................................64 Suggested action......................................................................................................64 While editing the settings of guest VMs created by server migration, an invalid OS ID warning appears.......................................................................................................................64 Suggested Action...........................
Part I Overview and concepts This part focuses on conceptual information needed to understand the product. It does not include information on how to use server migration.
1 Server migration introduction Overview HP Insight Control server migration provides an automated, accurate and affordable way to migrate existing servers running Microsoft Windows or Linux and their content to the latest ProLiant server technologies or the latest virtualization platforms from VMware and Microsoft. Insight Control server migration supports the following types of Microsoft Windows and Linux migrations: • Physical-to-ProLiant (P2P) migration—Migrates a physical machine to a ProLiant server.
Table 1 Related products (continued) Product Description settings, so that each computing device is maintained in the right configuration. Insight Control server deployment A server deployment solution that facilitates the installation, configuration, and deployment of large server volumes through a GUI-based or a web based console, using scripting or imaging technology.
2 Server migration concepts Server migration components The Insight Control server migration environment consists of the following required components: • Application station—The computer from which the migration is set up and performed. This can be either a physical machine or a Windows guest on a supported hypervisor. In earlier versions of Insight Management, the standalone installation of Insight Control server migration software was enabled.
HP Insight Control server migration software tabs Figure 1 Migration screen The Insight Control server migration software page has the following tabs: • Migration Wizard This tab enables you to perform the Insight Control server migration.
provides the option to upload the DevCon binary. For more information about this tab, see “Uploading drivers” (page 33). • Deploy Agent This tab enables you to deploy the Insight Control server migration Source Agent and PINT Agents.
Part II Pre-migration tasks This part of the guide assists you in collecting information to prepare for a migration, and covers steps 1 and 2 of the “Migration checklist” (page 12)
3 Preparing hardware for migration Verifying hardware and operating system support Before starting an X2P (P2P or V2P) migration, verify the following: • The source server operating system is supported on the destination server. To verify OS support on ProLiant destination servers, see the following website: http://www.hp.com/go/ossupport • For the supported hardware and software configurations of server migration, see HP Insight Management Support Matrix available at: http://www.hp.
4 Planning the migration Planning a migration strategy One challenge when migrating operating systems, applications, and data is modifying the migrated operating system to boot on the destination server and to function properly on the hardware. Insight Control server migration makes the required operating system changes for you. To best prepare for a migration, consider developing a migration strategy before running a migration.
RAW (partitions in which no file systems exist). Although server migration can perform migrations on these volumes, it cannot resize the volumes. • Volumes with bad clusters. The migration of volumes with bad clusters is not supported by server migration and requires that you manually migrate volumes with bad clusters to the destination server after a migration. If an NTFS volume is detected but cannot be resized, you must run a disk check (for example CHKDSK.
5 Preparing software for migration Verifying licenses for software to be migrated Before performing a migration, review all hardware, operating system, and application licenses on the source server and acquire all valid licenses necessary for the destination server. Some hardware, software, and operating systems license agreements might require you to purchase a new license for the destination server.
Figure 2 TCP ports in use during migration NOTE: Insight Control uses the following encryption types: • SSL RSA with RC4 128 MD5 • SSL RSA with RC4 128 SHA • TLS RSA with AES 128 CBC SHA cipher suites Disabling antivirus software For optimal performance during migration, verify that real-time scanning is temporarily disabled and that no antivirus scans are running or are scheduled to run while the migration is performed on the application station, source server, or virtual machine hosts.
Part III Migration This part of the guide contains information related to steps 3 through 5 of the“Migration checklist” (page 12), and methods for manually completing some the steps of the migration wizard. Remember, this guide does not describe each of the steps in specific detail — you can find specific information in the online help.
6 Preparing the source server and deploying the Source Agent Verifying Windows source server requirements The physical or virtual Windows source server requires the following: • User account credentials with administrative rights • A supported Windows operating system. For a list of operating systems, see the HP Insight Management Support Matrix available at: http://www.hp.com/go/insightmanagement/ docs.
• To enable the display of the Linux source server agent in 64–bit RHEL, you must install the X.Org X11 libXtst runtime library libXtst-1.0.99.2-3.el6.i686.rpm. • The 32-bit version of glibc is required to run the Linux server migration Source Agent. The library is present by default on 32-bit Linux installations, but you may need to install it manually on 64-bit Linux systems. The 32-bit version of glibc is available on your Linux OS installation CD/DVD.
Use one of the following methods (for additional information on these procedures, see the server migration online help): • • HP Systems Insight Manager ◦ Choose Deploy→Deploy Drivers, Firmware and Agents→Install server migration Agent. ◦ Using the QuickLaunch feature, select a source server, hover your mouse over the Quick Launch link, and then select Install server migration agent.
Figure 4 Server migration agent install dialog When the server migration Source Agent is ready for migration, the following screen appears on the source server.
4. Record the IP addresses listed for the source server entry when using Insight Control server migration. After the application station is connected to the migration Agent on these servers, the agent is locked to the application station. CAUTION: The agent deployment automatically opens the necessary ports in the firewall. These ports will remain open unless manually closed later using your firewall software. 5.
Figure 7 Linux Source Agent screen NOTE: The server migration Source Agent uses a 32–bit Java Runtime Environment. In 64–bit RHEL, the Linux source migration agent window does not appear, although the agent is running. 4. Record the IP addresses listed for the source server. CAUTION: 5. The agent deployment automatically stops the firewall and disables SELinux. After the application station is connected to the migration agent on these servers, the agent is locked to the application station.
7 Preparing the destination server and deploying the destination agent Prerequisites Physical destination servers A supported ProLiant destination server must be used for X2P migrations, and the destination server disks must be configured to support migration of source servers. For a list of supported ProLiant servers for X2P, see the list of supported servers in the HP Insight Management Support Matrix at the following website: http://www.hp.
Linux server migration can fail with the following error if Destination Size, chosen when specifying destination disks in the migration wizard, does not have enough space to create the -smpue files: Server migration could not modify initrd on the destination server. This could happen when there is not enough free space available on boot partition.
Booting a physical destination server automatically using the migration wizard 1. 2. 3. 4. 5. 6. Identify the source server and select volumes to migrate in steps 1 and 2 in the server migration wizard. In step 3 of the P2P or V2P migration wizard, select Auto Boot - Let server migration boot the destination server. Enter the iLO IP address and iLO credentials. Enter the static IP address, subnet mask, and default gateway (if needed).
• Connect the boot virtual disk to the 0th channel of the first IDE controller. • The Insight Control server migration Virtual Machine Boot CD ISO is attached to the destination virtual machine. Prerequisites for VMware ESX migration Ensure that the following parameters are met: • The virtual machine has at least 1024 MB of memory. • Create the virtual machine by selecting the correct operating system being migrated. • Create the virtual machine with at least one Flexible Network Adapter.
NOTE: If the application is unable to connect to the destination virtual machine, return to step 3 of the migration wizard, and then, while leaving the migration wizard running, manually create a virtual machine in the VM Host Management console outside of the migration wizard. Return to the migration wizard and select Manual Boot — Manually create VM through VM Host's Infrastructure Client, specify the IP address of the destination virtual machine, and then continue with the migration.
8 Migrating the servers Prerequisites CAUTION: If the Insight Control application station shuts down or fails during any migration, then the migration fails. The application station must be available during the complete migration cycle for a successful migration. Minimum source server prerequisites for all migrations These prerequisites are the same for all migration types: P2P, P2V, V2P, or V2V.
website.) Do not extract the binary that you download from the Microsoft website before uploading it here. Preparing for a Windows server migration The following sections list prerequisites for a Windows server migration. If you use a firewall, see “Disabling firewalls” (page 19) . Comply with all minimum prerequisites as listed in “Minimum source server prerequisites for all migrations” (page 33).
• The primary storage controller is configured with drives attached. • The destination server is booted to the Insight Control server migration ProLiant Boot CD ISO and is running the migration agent. • Select Auto Boot option in step 3 of the migration wizard.
Source virtual machine prerequisites If migrating from a source virtual machine, verify that the following prerequisites are complete: • Comply with all minimum prerequisites as listed in “Minimum source server prerequisites for all migrations” (page 33). • PermitRootLogin and PasswordAuthentication are set to Yes in the /etc/ssh/ sshd_config file and the sshd service is running. • The GRUB Boot Loader is the primary boot loader on the source server. • Guest tools are uninstalled.
4. 5. Follow the relevant migration steps in “Preparing for a Windows server migration” (page 34). In step 5 (Specify destination disks) of the migration wizard, verify that you have selected the boot LUN that you configured in the HBA BIOS of the destination server when you migrate the boot partition on the source server. NOTE: To migrate Windows 2003 to a SAN-connected destination server, you must first install Service Pack 2, and the updated Storport storage driver (see http://support.microsoft.
3. Systems Insight Manager verifies the source server or source virtual machine. • If the selected server or virtual machine fails to satisfy the criteria to launch Insight Control server migration migration, then the Systems Insight Manager task wizard appears, the Next button is disabled, and the migration cannot proceed.
4. 5. Click Show Host to view the server IP address, name, and OS details. If you manually deployed the Source Agent, click Next now, otherwise check Deploy Insight Control server migration Source Agent and then click Next. Refer to the server migration online help for information about completing the rest of the steps in the server migration wizard.
Figure 11 Available operations 3. 4. Systems Insight Manager verifies the source physical server or source virtual machine. • If the selected server or virtual machine fails to satisfy the criteria to launch Insight Control server migration, then the Quick Launch list does not display the unsupported migration options.
9 Post-migration tasks Installing ProLiant Support Packs after migration If you performed a Windows X2P migration, and you did not upload the Windows PSP executable from the Upload Drivers tab prior to migration, then you must manually install the HP ProLiant Support Pack (PSP) after a migration on the destination server. You can configure Insight Control server migration to automatically install a PSP after the Windows migration is completed on Step 6 of the migration wizard, Additional Migration Options.
3. (Optional) Add a CD-ROM component to the destination virtual machine. The CD-ROM might be required to install additional Integrated Components. After the virtual machine reboots, you must perform the following steps on the destination virtual machine guest for hypervisors. 1. Modify the system host name. 2. Install the proper Guest tools. 3. Check the network connections and re-establish network connectivity.
4. If the source and destination servers must be on the network at the same time: a. Change the host name of either server or consider reconfiguring the applications. b. If the IP addresses are static, reassign them. 5. 6. If the license is not a volume license, then reactivate it. The mouse and keyboard might not be immediately active after the migration. Wait until all required drivers are automatically installed by the guest operating system.
2. 3. 44 Compare the source and the destination server to ensure that the partitions selected on the source server are present on the destination server. Compare random samples of files and directories between the source and the destination servers to ensure that the data has been migrated successfully.
Part IV Troubleshooting and support
10 Troubleshooting Register to receive customer advisories via email. See the HP Insight Management Installation and Upgrade Release Notes at the following website: http://www.hp.com/go/insightmanagement/docs User interface Server migration wizard hangs Wizard hangs if the Ctrl key is pressed while selecting tabs in Insight Control server migration. Cause Tabs in HP Insight Control server migration cannot be treated like hyperlinks.
Cause Some versions of Windows Server 2003 that are pre-installed by HP cannot be migrated successfully unless corrective action is performed before attempting the migration. Affected systems are detected by the server migration Source Agent during initialization. If the system is affected, instructions for performing the corrective action are provided. If you attempt the migration without first performing the corrective action, your destination server becomes non-bootable.
Suggestion action Try the following: • Verify that you have provided valid credentials with administrative rights for the source server for the migration agent deployment. • If the source server has Insight Control server migration installed, ensure that you have disabled the server migration application and web services from the Windows services console. • The ports reserved for the migration agent (51124 through 51126) might be used by other processes.
Failed to deploy server migration Source Agent. Error while installing the server migration Source Agent on the given Server : exec tar -zxf hpsmpagent.tar.gz -C /tmp on the remote host failed. The ports 51124, 51125 and 51126 required by the agent might be in use. : exec tar -zxf hpsmpagent.tar.gz -C /tmp on the remote host failed. The ports 51124, 51125 and 51126 required by the agent might be in use. Suggested action To resolve this issue, the Linux Source Agent must be deployed using root privileges.
2. 3. 4. Verify that the destination server is booted from the Insight Control server migration Boot CD ISO and ready for migration. Verify that the destination server can be reached from the application station and source server. Communication on network ports 51125 and 51126 must be enabled by any firewall between the CMS, the source server, and the destination server. Verify that another Insight Control application is not already communicating with the destination server.
You can confirm this by accessing the Configure Destination Server screen and then clicking Launch Array Configuration Utility or by rebooting to Option ROM Configuration for many controllers (ORCA). Primary controller configured in the system does not have drives attached Suggested action Confirm that your hardware setup is correct and that the correct controller is set to primary in ROM-Based Setup Utility (RBSU).
Some storage volumes on the destination server are not available for selection Some storage volumes configured on the destination server might not be available for selection in Step 5 (SpecifyDestination Disks and Resize NTFS Partitions) of the migration wizard. Suggested action If expected volumes do not appear, perform one of the following: • Verify that the storage controller is supported by Insight Control server migration.
Insight Control might not detect virtual machines on mapped network drives Cause Insight Control cannot locate virtual machines stored on mapped network drives if the service does not have access to the network shares. Suggested action Manually migrate these disks after a successful migration.
Suggested action To resolve this issue, manually boot the destination server, and then manually assign the IP address to the NIC that is on the same network as the application station. To resolve the gateway issue, ensure that you enter the gateway IP address in the migration wizard when identifying the destination server.
Server Migration failed. Error occurred in server thread; nested exception is: java.lang.OutOfMemoryError Suggested action Server migration does not support the migration of volumes larger than 1023 GB. Reduce the size of any partition exceeding this size limit before attempting migration.
Partitions created with third-party partitioning tools do not show proper file system type in the server migration wizard Partitions created with third-party partitioning tools such as Gnome might not show the proper file system type in the server migration wizard. This does not affect migration. Suggest action Proceed with the migration.
1. Execute the following command on the source server and note the output: cat /proc/sys/vm/drop_caches 2. Execute the following commands on the source server: echo 3 > /proc/sys/vm/drop_caches echo
Suggested action Restart the application station and retry the migration. Starting a new migration after a current migration is stopped If a migration is stopped by means other than a cancellation or failure, the application station, source server, and destination server might not recognize that the migration has stopped. Suggested action To start a new migration: 1. Restart the migration agent on the source and destination servers. 2. On the application station, close the migration wizard. 3.
Cause There could be bad blocks on the source or destination disk. Suggested action Insight Control does not support migrations of disks with bad blocks. If the bad block is on the destination disk, change the destination disk. SAN-connected destination server displays blue screen Suggested action To migrate Windows Server 2003 to a SAN-connected destination server, install the following on the source server: • Service Pack 1 • Service Pack 2 • Updated Storport storage driver (see http://support.
Suggested action Perform one of the following: • Remove the System_drive\WINDOWS\Temp\hp_sum\RepositoryManager directory on the Insight Control server migration application station and retry the deployment. • Manually install the server migration Source Agent or PINT on the source server.
NOTE: After successfully using DevCon during a migration, Windows Device Manager may show yellow exclamation points (!) next to duplicate keyboard and mouse entries. Right click on the device with the yellow exclamation point and update the driver. The device should be rediscovered and changed from an unknown device to be an HID device. Devices which cannot be rediscovered using this method are duplicates and can be uninstalled using the right-click menu.
Reinstall the mouse and keyboard drivers with one of the following methods: • ◦ Reinstall the PSP ◦ Update the drivers in the Device Manager If all of the following criteria are met: ◦ the source server has a PS/2 mouse and keyboard ◦ the destination server has a USB mouse and keyboard ◦ the destination mouse and keyboard do not work then use the following procedure: 1. Attach a USB mouse and keyboard (using a USB or PS/2 dongle) to the source server. 2.
Drives do not appear on the migrated operating system After a successful migration, some migrated volumes do not appear in Windows Explorer. Suggested action Depending on the operating system, perform the following task to assign a driver letter to the volume so it is visible in Windows Explorer: 1. For Windows Server 2003 systems—Select Control Panel→Administrative Tools→Computer Management→Disk Management, and then verify that the disk manager has initialized all disks. 2.
might also appear when a virtual machine is migrated from one Microsoft Hyper-V host to another Hyper-V host. You might be unable to assign the IP address to this device, which does not reappear on the Network Connections Page. Suggested action Manually uninstall the Network adapter in the Device Manager and trigger a Scan for Hardware Changes. This detects the NIC adapter and configures the drivers for it.
Suggested action Reboot the server and then reinstall PSP manually. Destination server still shows server migration UI but server migration Wizard shows migration completed After the migration, server migration losses connectivity to Hyper-V host, which causes server migration to fail to eject the boot CD and reboot the VM. If server migration is unable to connect Hyper-V host, then reboot using the destination agent.
11 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support: • See the Contact HP worldwide website: http://www.hp.
Warranty information HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty applies to all Insight Management products. HP authorized resellers For the name of the nearest HP authorized reseller, see the following sources: • In the United States, see the HP U.S. service locator website: http://www.hp.com/service_locator • In other locations, see the Contact HP worldwide website: http://www.hp.
6. 7. 8. Scroll down the page until you see the table labeled Software - Support Pack. Select the PSP link in the Description column. To download the PSP, select the Download>> button associated with the *.tar.gz (gzipped) file. To view or download the associated HP ProLiant Support Pack User Guide, select the Release Notes tab.
CAUTION An alert that calls attention to important information that, if not understood or followed, results in data loss, data corruption, or damage to hardware or software. IMPORTANT An alert that calls attention to essential information. NOTE An alert that contains additional or supplementary information. TIP An alert that provides helpful information.
A Applying old server migration standalone licenses Starting with Insight Control 6.0, HP Insight Control server migration is no longer available as a standalone and is available exclusively through Insight Control. The addition of server migration functionality into HP Insight Control is a function of the Insight Control software, not of the license key or the part number. There are no new part numbers needed for the addition of server migration functionality.
B Performing migrations in a Microsoft Cluster server environment Migrations in a Microsoft Cluster server environment often require you to move an operating system, appropriate applications, and data to new server hardware. In a cluster, various applications such as Microsoft Exchange, Microsoft SQL Server, or a file share can be installed. Cluster migration includes moving these additional resources.
2. 3. 4. 5. 6. 7. 8. 9. Review the event logs and cluster logs to verify that there are no critical issues that might affect the migration. If an Exchange or SQL Server is installed on the cluster, the pre-migration steps are similar to those of a standalone Exchange or SQL Server. The only deviation from this procedure is that you would not need to set services to Manual. (By default, all the Exchange and SQL Server services are set to Manual.
15. Review the event logs and cluster logs to see if there are any issues occurring with the newly migrated cluster.
Glossary ESX VMware ESX, a virtualization product produced by VMware, Inc.
Index A antivirus software, 20 application station description, 12 fails to connect to the destination server for X2P, 53 auto booting destination server fails, 52 B blue screen error X2P migration, 54 boot disk cannot be installed or injected with drivers, 54 boot disk cannot be installed or injected with drivers in log file, 57 booting the destination server, 29 manually creating and booting a virtual machine, 30 migration wizard for a virtual destination, 31 prerequisites for Microsoft Hyper-V, 30 prere
K kernel panic when booting to the Insight Control CD ISO, 50 keyboard does not work when booting to the Insight Control CD ISO, 50 troubleshooting, 60, 61, 63 L launching migration wizard, 37 migrations through Quick Launch, 39 migrations through Systems Insight Manager, 37 licenses overview, 10, 13 standalone documentation, 70 verifying, 19 Linux data copy error, 58 deploying Source Agent, 26 destination physical server prerequisites, 36 destination size requirement, 28 destination virtual machine prereq
application station requirements, 16 application station system requirements, 16 choosing server migration Agents, 23 critical or hardware-dependent applications , 18 Linux server migration, 35 migration checklist, 12 source server operating system support, 16 uninstalling guest tools, 23 Windows server migration, 34 primary controller does not have drives attached, 51 does not have logical drives defined, 50 not supported, 51 ProLiant Support Pack see PSP PSP documentation, 67 downloading, 67 installing Wi
W websites HP documentation, 67 ProLiant Support Pack, 67 Windows destination physical server prerequisites, 34 destination virtual machine prerequisites, 35 installing PSP after migration, 41 installing PSP before migration, 20 P2P post-migration tasks, 41 P2V post-migration tasks, 41 preparing for a server migration, 34 SAN migration, 36 source physical server prerequisites, 34 source virtual machine prerequisites, 34 unrecoverable sector-read errors, 58 USB mouse or keyboard do not work, 61 Windows serve
