HP Insight Control Server Migration 6.2 User Guide HP Part Number: 461487-006 Published: October 2010 Edition: 6.
© Copyright 2010 Hewlett-Packard Development Company, L.P. 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.
Table of Contents I Overview and concepts................................................................................................11 1 Server migration introduction.................................................................................13 Overview.........................................................................................................................................13 Installing and configuring server migration software.........................................................
Preparing a Microsoft Hyper-V source server...........................................................................31 Verifying Linux source server requirements...................................................................................31 Uninstalling guest tools...................................................................................................................31 Choosing server migration agents.........................................................................................
9 Post-migration tasks.................................................................................................51 Installing ProLiant Support Packs after migration..........................................................................51 X2P post-migration tasks (Windows)..............................................................................................51 X2V post-migration tasks (Windows).............................................................................................
Suggested action...................................................................................................................61 Application station fails to connect to the destination server....................................................61 Cause.....................................................................................................................................61 Suggested action........................................................................................................
Large volumes fail with server thread error..............................................................................66 Suggested action...................................................................................................................66 Migrating a Linux source server with very large storage fails when the migration is initiated.......................................................................................................................................66 Suggested action.......
Migration does not start after confirmation. The event log continuously displays Operation Migration waiting for connection to source...............................................................................72 Suggested action...................................................................................................................72 Destination server mouse and keyboard do not work after a Windows migration..................72 Suggested action...................................................
A Applying old SMP standalone licenses.....................................................................81 Adding standalone Insight server migration licenses..........................................................................81 B Performing migrations in a Microsoft Cluster server environment...........................83 Premigration consideration steps for clusters......................................................................................83 Performing the migration....................
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, Microsoft, and Citrix.
Table 1-1 Related products Product Description PINT and PISA These tools are available on the Insight software DVD. These tools are loosely integrated with the migration function. Refer to the associated README on the DVD. HP OpenView Change and Configuration Management Automates the management of software such as operating solutions systems, applications, patches, content, and configuration settings, so that each computing device is maintained in the right configuration.
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 virtual machine running a supported Windows operating system, running as a guest on a supported hypervisor.
HP Insight Control server migration software tabs Figure 2-1 Migration screen The Insight Control server migration software page has the following tabs: • License This tab enables you to view the number and types of older Server Migration for ProLiant or SMP licenses available. For more information about licensing, see Appendix A: “Applying old SMP standalone licenses” (page 81). • Migration Wizard This tab enables you to perform the Insight Control server migration.
• View Status/Logs This tab enables you to view the details and results of attempted migrations and to delete migration results. For more information about viewing logs, see “Viewing migration logs” (page 53). • Upload Drivers This tab displays the status of the iSCSI Initiator installed on the server and provides the option to upload PSP executable files. For more information about this tab, see “Uploading drivers” (page 43).
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 15) 19
3 Preparing hardware for migration Verifying hardware and operating system support Before beginning a migration, verify that the source server operating system is supported on the destination server or host by HP and that the operating system is supported for the migration type selected. Because the Insight Control server migration wizard does not block migrations of unsupported operating systems, you must verify that the selected operating system is supported before beginning the migration.
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.
• • Large NTFS partitions or NTFS partitions with too many clusters, resulting in large volume cluster bitmaps that cannot be resized. In some cases, the volume might be recognized as 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.
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 5-1 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 Changing the default Insight Control server migration application station service port number By default, Insight Control server migration uses port 51124 as the default port for communications.
1. 2. For Windows X2P migrations, upload the PSP you plan to use on the Upload Drivers tab of the server migration wizard. This operation copies the PSP to the CMS, where it can be accessed automatically as needed. For Linux X2P migrations, you must manually apply the Linux PSP to the destination server after the migration is complete.
Part III Migration This part of the guide contains information related to steps 3 through 5 of the“Migration checklist” (page 15), 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.
normal functioning of the network adapters, keyboard, and mouse. After the migration is completed, you can reinstall the guest tools on the source virtual server. Choosing server migration agents Deploy and run migration agents on the source server and the destination server before starting a server migration.
Figure 6-1 Navigate to server migration Source Agent 2. 3. Copy the cp009582.exe file to the source server, and then run the file. If a security warning window appears, click Run . To launch the server migration Source Agent, click Install. Figure 6-2 Server migration agent install dialog When the server migration Source Agent is ready for migration, the following screen appears on the source server.
Figure 6-3 Windows Source Agent screen 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: 5. The agent deployment automatically stops the firewall.
Deploying a server migration Source Agent on a Microsoft Small Business Server Microsoft Small Business Server operating systems include a domain controller on the server. Follow the steps in “Deploying a server migration Source Agent on domain controllers” (page 34)to ensure successful migration of Small Business Server. Deploying the Linux server migration Source Agent locally on the source server 1.
Figure 6-5 Linux Source Agent screen 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 P2P or V2P migrations, and the destination server disks must be configured to support migration of source servers. For a list of supported ProLiant servers for P2P and V2P, see the list of supported servers in the HP Insight Software Support Matrix at the following website: http://www.hp.
files or make sure that boot partition has 10MB or more of free space and retry migration process. To resolve this issue, choose a Destination Size, when specifying destination disks in the migration wizard, that is large enough to create the /boot/-smpue files on the corresponding disk partition on the destination server. Booting the destination server Boot the destination server using the applicable Insight Control server migration Boot CD ISO.
iLO boot prerequisites The following requirements must be met to use the boot from iLO feature: • The iLO user credentials provided must have Virtual Power and Reset and Virtual Media access applied. • The browser must be configured to support HTTP 1.1. To add this support: 1. On your web browser, open Internet Options, and then select the Advanced tab. 2. As appropriate, select Use HTTP 1.1 and Use HTTP 1.1 through proxy connections .
• The Insight Control server migration Virtual Machine Boot CD ISO is attached to the virtual boot disk you create. Prerequisites for VMware ESX migration Ensure that the following parameters are met: • The virtual server has at least 600 MB of memory. • Create the virtual server by selecting the correct operating system being migrated. • Create the virtual server with at least one Flexible Network Adapter. • Connect the network adapter to a virtual network switch that is connected to an external network.
5. If the application is unable to connect to the destination virtual server, return to step 3 of the migration wizard, and then, while leaving the migration wizard running, manually create a virtual server 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 server, 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.
• • • • • Verify that a Windows NT boot loader (NTLDR) is installed. During migration, the migration agent initiates an operating system reboot on the source physical server. Verify that the operating system is on the first boot order. The Insight Control application supports migration of source physical servers that have operating systems installed on the primary drive (Hard Disk 0) and the primary drive loaded first in the boot order.
• Temporarily disable any antivirus software auto-scans on the destination virtual server host to prevent interrupting the migration process. Re-enable the antivirus software after the migration. Preparing for a Linux server migration The following sections list prerequisites for a Linux server migration. • If you use a firewall, see “Disabling firewalls” (page 25). • Verify compliance with all minimum prerequisites. See “Minimum source server prerequisites for all migrations” (page 43).
SAN migrations in Windows IMPORTANT: SAN migrations are not supported for Linux servers. Insight Control supports Windows migrations to destination physical servers with Fibre Channel SAN connectivity. To verify that your Fibre Channel HBA is supported, see the Insight Software Support Matrix at the follow website: http://www.hp.
2. 3. From the main wizard, select Deploy→server migration Tools, and then select the appropriate migration option. Systems Insight Manager verifies the source server or source virtual server. • If the selected server or virtual server fails to satisfy the criteria to launch Insight Control migration, then the Systems Insight Manager task wizard appears, the Next button is disabled, and the migration cannot proceed.
Figure 8-2 Identify the source server 4. 5. Click Show Host to view the server IP address, name, and OS details. If the proper host information appears, click Next. Refer to the server migration online help for information about completing the rest of the steps in the server migration wizard. Launching server migrations through Quick Launch To launch an Insight Control migration from Systems Insight Manager using the Quick Launch option, perform the following tasks: 1.
Figure 8-3 Quick Launch • From All Systems page in the Systems Insight Manager console, select a source server, and then scroll over Quick Launch. Quick Launch displays the available operations with the selected source virtual server or source server.
3. Systems Insight Manager verifies the source physical server or source virtual server. • If the selected server or virtual server fails to satisfy the criteria to launch Insight Control migration, then the Quick Launch list does not display the unsupported migration options. • If the selected server or virtual server meets the criteria, then the Insight Control server migration application opens in a new browser with the IP address of the selected host added in step 1 of the migration wizard. 4.
9 Post-migration tasks Installing ProLiant Support Packs after migration If you performed a Windows P2P or V2P migration, and you did not upload the Windows PSP executable from the Upload Drivers tab prior to migration, then you must install the HP ProLiant Support Pack (PSP) following 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.
After the virtual server reboots, you must perform the following steps on the destination virtual server 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. If an IP address conflict occurs when setting the static IP address, see the following website for more information: http://support.microsoft.com/kb/269155/ 4. 5. 6. 7.
b. 5. 6. If the IP addresses are static, reassign them. 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. X2V post-migration tasks (Linux) After you complete a P2V migration, perform the following steps on the destination server: 1.
2. 3. 54 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 55
10 Troubleshooting Register to receive customer advisories via email. See the Insight Software Installation and Upgrade Release Notes at the following website: http://www.hp.com/go/insightsoftware/docs Installation This section describes troubleshooting procedures for issues concerning installation of Insight Control server migration.
3. 4. 5. 6. 7. 8. Note the process identifier numbers (PIDs) for ports 51124, 51125, 51126, and 51127. Open the Windows Task Manager, and then click the Processes tab. Click View→Select Columns. Select PID (Process Identifier), and then click OK. Locate the PIDs in the PID column that were identified in step 3, and then determine the service that is currently using the ports needed for Insight Control. Contact your system administrator to release these ports.
Source server identification fails The source server identification fails during the first step of the migration wizard. Suggested action 1. 2. 3. 4. Verify the identifier entered. If the name is entered for a source server that is in a domain, be sure that the Fully Qualified Domain Name (FQDN) is entered. Verify that the migration agent has been installed on the identified source server. For more information about running the migration agent, see the Insight Control server migration online help.
• A "Client for Microsoft Networks" client must be added to the network interface properties on the application. Remote deployment of Linux Source Agent using non-root credentials fails Remote deployment of Linux Source Agent using non-root credentials fails with the error: 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.
bcdedit /set hypervisorlaunchtype auto • Remove the Microsoft Hyper-V role from the source server. Destination preparation Destination server identification fails The destination server identification fails in step 3 of the Wizard. Suggested action 1. 2. 3. 4. Verify that the network adapter on the destination server is configured with a valid IP address, subnet, and gateway. Also verify the network configuration information reported on the destination server.
Kernel panic occurs when booting a virtual machine to the Insight Control server migration Virtual Machine Boot CD ISO Insight Control server migration requires that the destination virtual machine has at least 600 MB of RAM to boot to the Insight Control server migration Virtual Machine Boot CD ISO. Suggested action To resolve this issue: 1. Power down the virtual machine. 2. Ensure that the virtual machine has at least 600 MB of RAM. 3.
3. If the Insight Control server migration Boot CD ISO cannot detect the storage controller, you may need to reconfigure the storage controller environment variable. a. Reboot the destination server to Rom-Based Setup Utility (RBSU) by pressing the F9 key during POST. b. Select the Boot Controller Order option and verify the proper boot order for the storage controllers. c. Press Esc to exit RBSU, and then press F10 to confirm the exit and to save your changes. d.
Static IP address cannot be assigned on the destination server while booting using the Boot CD ISO Assigning a static IP address on the destination server might result in an error similar to the following: The IP address xxx.xxx.xxx.xxx you have entered for this network adapter is already assigned to another adapter. Cause This might occur if the IP address is assigned to another network adapter on the destination server.
• • Automatic booting fails with the error Could not get timely response from remote management. Please try again or use manual boot option. in the migration wizard. Automatic booting continues for over 40 minutes without any error messages displayed in the migration wizard. Suggested action Reset the iLO on the destination server, and then reboot the destination server or manually boot the destination server. For more information on iLO, see the iLO user guide.
Migration process Drivers cannot be installed or injected onto boot disk This error is reported if Insight Control fails to install or inject device drivers. In most cases, additional information is reported on the destination server. Suggested action Possible causes and solutions for this error include: • The boot partition was not migrated to the boot volume on the destination server. Verify that the boot partition is selected for migration and placed on the boot volume of the destination server.
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 now show the proper file system type in the server migration wizard. This does not affect migration. Suggest action Proceed with the migration.
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. Destination VM not powered off on HP integrated Citrix XenServers During X2V migrations to a destination VM on an HP integrated Citrix XenServer, the VM is not powered off even when you select the The destination server should be powered off after migration completes option. Suggested action You must manually power off the VM after the migration is complete.
3. Before starting a new migration, verify that all antivirus and firewall software is properly reconfigured or disabled. Error during data copy of Linux migration An Error during data copy offset=offset srcPos=source sector dstPos=destination sector amount=number of sectors message appears in the source or destination log followed by a I/O Exception. 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.
Windows server migration Source Agent or PINT remote deployment fails with Agent is already deployed or not required error When you remotely deploy the Windows server migration Source Agent or PINT from the Insight Control server migration application station or from Systems Insight Manager, the server migration Source Agent deployment fails with the error Agent is already deployed or not required.
Migration does not start after confirmation. The event log continuously displays Operation Migration waiting for connection to source When the migration starts, the source server reboots and runs the migration agent in exclusive mode during migration. Rebooting the source machine might take a few minutes. If this process takes a long time, verify that the source machine is rebooted with the migration agent running in exclusive mode. The source machine might be waiting for user input during the reboot.
drivers. In some scenarios, the USB keyboard and mouse drivers may fail to load. Example scenarios include a tampered source, a Microsoft Hyper-V VM source, or a migrated source that used PS/2 drivers. Suggested action • • Reboot the destination server a second time after the migration. During the reboot, verify Legacy USB is set to Enabled in the BIOS on the destination server. The Plug and Play drivers should load automatically through the Hardware Setup Wizard.
Mouse does not work on the destination ESX virtual machine after a V2V migration The mouse might stop working on the destination ESX virtual machine after a V2V migration. Suggested action To resolve this issue, use the following procedure: 1. Log in to the destination server using the keyboard. 2. Press the Windows Key+Pause/Break to open System Properties. 3. Use the arrow keys or Tab key and the Enter key to open Device Manager. 4.
Static IP address cannot be assigned on the destination server after migration Assigning a static IP address on the destination server might result in an error similar to the following: The IP address xxx.xxx.xxx.xxx you have entered for this network adapter is already assigned to another adapter. This scenario can occur if the IP address is assigned to a network adapter on the source server. Suggested action For more information, see the following website: http://support.microsoft.
While editing the settings of guest VMs created by server migration, an invalid OS ID warning appears After performing an X2V migration to an ESX Host using the Automatic Boot feature of the server migration wizard and then changing the settings of the migrated VM, the following warning message may display: The guest OS ID is not valid. Suggested Action Follow the suggestion provided in the warning message to resolve the issue.
11 Support and other resources Contacting HP 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 technical support Use the following methods to contact HP technical support: • In the United States, see the Customer
• HP Insight Control Documentation for Insight Control, including documentation for Insight Control virtual machine management and Insight Control power management, is available from the HP Insight Control website: http://www.hp.com/go/insightcontrol/docs Websites HP ProLiant Support Pack To find and download the HP ProLiant Support Pack (PSP) that is appropriate for your ProLiant server and Linux OS, follow these steps: 1. Open a browser to the following web address: http://www.hp.com 2. 3. 4.
Ctrl+x or Ctrl-x A key sequence that indicates you must hold down the keyboard key labeled Ctrl while you press the letter x. ENVIRONMENT VARIABLE The name of an environment variable, for example, PATH. Key The name of a keyboard key. Return and Enter both refer to the same key. Term A term or phrase that is defined in the body text of the document, not in a glossary. User input Indicates commands and text that you type exactly as shown.
A Applying old SMP 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 premigration 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.) 3.
14. Perform the Exchange or SQL post-migration steps on the cluster, as described later in this white paper. 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, 26 application station description, 15 fails to connect to the destination server, 61 fails to connect to the destination server for P2P or V2P, 65 auto booting destination server fails, 64 B blue screen on destination server, 71 Boot CD ISO might stop responding when exiting the Array Configuration Utility, 63 boot disk cannot be installed or injected with drivers, 66 boot disk cannot be installed or injected with drivers in log file, 68 booting the destination server, 38 manua
kernel panic when booting to the Insight Control CD ISO, 62 keyboard does not work when booting to the Insight Control CD ISO, 62 troubleshooting, 72, 74 virtual server, 39 menus missing, 58 Microsoft Cluster migration overview, 83 post-migration, 84 preforming the migration, 84 premigration, 83 migration different drive letters after migration, 74 does not terminate if source server is shut down, 67 fails with the Microsoft Hyper-V role enabled, 60 Microsoft Cluster server environment, 83 starting a new o
using the migration wizard, 40 physical destination servers prerequisites, 37 Physical-to-ProLiant migration (see P2P) Physical-to-virtual migration (see P2V) planning migration strategy, 23 preparing a schedule, 23 port changing default, 26 ports unavailable, 57 used, 25 post-migration troubleshooting, 71 post-migration tasks editing the Windows Boot.
post-migration, 71 source preparation, 58 uninstallation, 76 user interface, 58 types of migration, 13 typographic conventions, 78 U uninstalation troubleshooting, 76 uninstall unable to uninstall an older version of migration software, 76 uninstalling guest tools, 31 upgrading server migration software, 13 user interface troubleshooting, 58 V V2P, 13 source server prerequisites, 43 V2V, 13 booting a virtual destination server, 40 source server prerequisites, 43 using the migration wizard, 40 validating t
