Insight Control server migration User Guide HP Part Number: 461487-005 Published: January 2010 Edition: 6.
© Copyright 2007, 2010 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.
Table of Contents 1 Introduction.............................................................................................11 Insight Control server migration...............................................................................................................11 Insight Control server migration benefits...................................................................................................11 Insight Control server migration platform support..............................................
Booting the destination server for P2P, V2P, and X2V migrations.................................................................29 Manually booting a physical destination server using the Insight Control server migration Boot CD for P2P and V2P.........................................................................................................................................29 Booting a destination server using the Insight Control Migration Wizard.................................................
Performing a V2P migration..............................................................................................................91 V2P post-migration tasks.................................................................................................................101 Virtual-to-ProLiant (V2P) migrations for Linux............................................................................................102 Preparing for a V2P migration.............................................................
Manual installation of Linux source agent using sudo user privileges fails...............................................150 Destination preparation.......................................................................................................................150 Destination server identification fails.................................................................................................150 Application station fails to connect to the destination server.......................................
A PSP installation after an X2P migration of Windows 2000 Server to a server with the Emulex LPe1105-HP 4Gb FC HBA might cause a blue screen on the destination server..................................158 Migration does not start after confirmation. The event log continuously displays Operation Migration waiting for connection to source .................................................................................................................
List of Tables 1-1 3-1 3-2 5-1 5-2 5-3 5-4 5-5 6-1 8-1 Related HP products for extending deployment....................................................................................16 Server and agent type.....................................................................................................................23 Restarting migration agents on source and destination servers...............................................................29 Concurrent migrations....................................
1 Introduction Insight Control server migration HP Insight Control server migration simplifies the server consolidation process. Insight Control server migrations involve moving an operating system, applications, and data from one server to another, instead of manually redeploying these elements on a new server. Insight Control server migrations allow you to migrate Windows and Linux operating systems to new compatible hardware.
Upgrading to Insight Control server migration from Insight Server Migration software for ProLiant You can upgrade the following: • Standalone Insight Server Migration software for ProLiant 3.0 or higher to standalone Insight Control server migration. • Insight Server Migration software for ProLiant 3.5 or higher installed from Systems Insight Manager to Insight Control server migration installed from Systems Insight Manager. Insight Control detects older versions upon installation.
server. For example, data on \PhysicalDrive5 on the source server during a Windows migration might be reordered to \PhysicalDrive2 on the destination server. During a Linux migration, data on /dev/sda on the source server might be reordered to /dev/sdc on the destination server. When performing a P2V or V2V migration, be sure your destination virtual machine host has adequate memory, processor resources, and disk space to migrate the source server partitions.
Virtual machine guest tools Before starting a migration, you must uninstall the guest tools if you are migrating a source virtual machine. The guest tools are not applicable on the destination server and might cause issues with the normal functioning of the network adapters, keyboard, and mouse. After the migration is completed, you can reinstall the guest tools on the source virtual machine. Domain controllers Insight Control supports migration of domain controllers.
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 Antivirus software For optimal performance during migration, verify 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.
You can resize ext2/3 and ReiserFS file systems on a Linux source server. ProLiant Support Pack IMPORTANT: The information in this section applies only to Windows P2P or V2P migrations. Insight Control does not install all drivers (including NIC drivers) on the destination server. To acquire the latest drivers, you must install the HP ProLiant Support Pack (PSP) following migration on the destination server.
2 Insight Control server migration installation and configuration requirements This chapter lists the hardware and software required for each component in the Insight Control environment.
NOTE: If the source server is an Insight Control server migration application station, the HP Insight Control server migration Application Service and HP Insight Control server migration Web Service must be stopped before agents are installed. Linux source servers The physical Linux source server requires the following components to be installed and running: • User account credentials with administrative rights • SELinux must be running in passive mode • A supported Linux operating system.
2. Click Install Application. The Welcome screen appears. 3. 4. Click Next. The License Agreement screen appears. Read the license agreement, select I accept the agreement, and then click Next.
5. Select the destination location for the Insight Control application. The default location is C:\Program Files\HP\HP Insight Control server migration. Click Next. 6. Enter the service credentials, and port changes if necessary, and then click Next.
NOTE: 7. To install Insight Control, you must have administrative rights. Click Finish.
Changing the default Insight Control server migration application station service port number By default, Insight Control server migration uses 51124 as the default port for communications. Use one of the following methods to change the port: • Change the port number during Insight Control server migration installation. • Manually change the port number after Insight Control server migration installation. 1. Edit the \bin\hpvmm.
3 Deploying migration agents Deploying server migration Source Agents Before starting a migration, the migration agent must be running on the source and destination servers. Therefore, verify the proper agent is applied to the source and destination server. To launch the migration agent, you must have administrative rights to connect to the source server. Before performing a migration, remove CDs, floppy disks, USB keys, or other detachable media from the source server.
Deploying the migration agent through the Insight Control CMS menu if Insight Control 6.0 is installed 1. 2. From the Insight Control toolbar, select Deploy→Drivers, Firmware and Agents. Select Install SMP agent, and then select the server to deploy to the agent. The Deploy Agent page appears when Insight Control is launched. 3. 4. From the Deploy Agent page, select the agent type, and then enter the credentials.
5. 6. Click Install Agent Now. View the deployment status and result of the migration agent. Deploying the server migration Source Agent directly from the Migration Wizard on the application station 1. 2. Log in to Insight Control by entering your User name, Password and Domain. Click the Migration Wizard tab. The Migration Wizard overview screen appears. 3. 4. 5. Select the relevant OS type and the migration option, and then click Next.
2. 3. Copy the file in this folder to the source server, and then run the file. If a security warning window appears, click Run on the window. To launch the server migration Source Agent, click Install. When the server migration Source Agent is ready for migration, the following screen appears on the source machine.
NOTE: 4. The following screen appears only if X Windows was used. 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. To unlock the connection between the application station and the source server, access the agent console on the source server, and then click Abort and Exit.
2. 3. Copy the file in this folder to the source server, and then extract the file. To launch the server migration Source Agent, go to the bin folder of the extracted directory, and then execute the script startHPSMPCnt.sh. When the server migration Source Agent is ready for migration, the following screen appears on the source machine. NOTE: 4. The following screen appears only if X Windows was used. Record the IP addresses listed for the source server entry when using Insight Control server migration.
To unlock the connection between the application station and the source server, access the agent console on the source server, and then click Abort and Exit. To stop the server migration Source Agent, on the source page, click Abort and Exit. CAUTION: NOTE: server. The agent deployment automatically stops the firewall and disables SELinux.
• To access the remote console, the iLO Advanced License must be applied. • At least 300 MB of free space for each iLO. Booting is required on the application station on the disk where Insight Control is installed. This space is recovered once the migration is completed or the boot job times out.
option. HP recommends booting the destination virtual machine from the application station using the auto boot option. The following sections list the special steps required to prepare virtual machines for boot to the Insight Control server migration Virtual Machine Boot CD. Microsoft Hyper-V migration • Ensure that the virtual machine does not have more than three disks attached. • Ensure that the virtual machine has at least 600 MB of memory.
Manually creating and booting a virtual machine destination server for P2V and V2V 1. 2. 3. Access the virtual machine host management console provided by VMware ESX, Citrix XenServer, or Microsoft Hyper-V. Create a new virtual machine with sufficient disk space for migration. Boot the virtual machine to the Insight Control server migration Virtual Machine Boot CD.
2. Review the system and storage configuration information to ensure the setup is correct. The system information section includes the following information: • RAM • Boot controller • Boot controller disk size • PCI device information (collapsed by default)–only applicable for X2P migrations If the boot controller disk size is zero or the controller is not supported, an error message appears under PCI device information.
3. (Optional) This step only applies to physical servers. To configure or reconfigure the HP array controllers, click Launch Array Configuration Utility. The Array Configuration Utility appears in a new window. The server reboots after exiting the Array Configuration Utility. For virtual servers, the Launch Array Configuration Utility button does not appear. 4. • To proceed with network configuration, click Next.
8. When a message appears advising you that the destination server is ready for migration: a. Record the IP address listed on the screen for the destination server entry when using the Insight Control application. b. Perform the migration from the application station. A message appears on the destination server that reports the migration progress when the data copy process begins.
If the migration agent fails to launch, an error message appears on the destination server. To reconfigure the network, click Previous. If the issue persists, reboot the destination server. NOTE: After completing a migration, the migration agent no longer runs on the destination server. After the application station is connected to the migration agent on the destination server, the agent is locked to the application station.
The Insight Server Migration software for ProLiant Overview screen has seven tabs: • Overview—This tab provides the following information or functions: • Types of server migrations supported • Migration steps overview • Option to set the Migration Wizard page as the default page. To enable this wizard to start by default, select Start the Migration Wizard when opening this application.
• Upload Drivers—This tab displays the status of the iSCSI Initiator installed on the machine and provides the option to upload PSP executables. For more information about this tab, see the Uploading drivers chapter in this guide. • Deploy Agent—This tab enables you to deploy the Insight Control server migration server migration Source Agents and PINT.
4 Licensing HP Insight Control server migration Licensing Insight Control server migration through the Insight Control license manager HP Insight Control server migration (previously known as HP Insight Server Migration software for ProLiant) can be installed with Insight Control 6.0. Server migrations are allowed to any system with an Insight Control license applied.
For products where licensing information is managed by Systems Insight Manager, the Assigning Licenses page appears. Select one or more systems from this list and click Assign License Now. The page refreshes and shows the updated license status. Select additional systems to make more assignments, or reselect License Manager to refresh the page.
The following types of standalone Insight Server Migration licenses have been available for purchase: • Subscription license—This type of Insight Server Migration license enables the consumption of an unlimited number of migrations for one year. The subscription period begins after the first license is consumed. • Demo license—This type of Insight Server Migration license enables a specific number of migrations for a specific period. The subscription begins after the first license is consumed.
5 Using Insight Control server migration to migrate servers After source and destination server agents are launched, you can start a migration from an application station or the Insight Control CMS by choosing one of the following: • To start the Migration Wizard from a stand-alone application station, double-click the Insight Control server migration icon on the desktop, or click Start→Programs→Insight Control server migration→Insight Control server migration.
NOTE: Insight Control server migration does not allow concurrent migrations with the same source or physical destination. Even though Insight Control enables you to concurrently migrate multiple source servers to the same host (X2V), HP does not recommended this type of migration because it affects the time required for the migration.
Source physical machine prerequisites • Verify that a valid network connection exists between the source and destination server. • Verify that the source server must contain an active boot partition to be migrated. • Complete any pending reboots and software installations on the source machine before initiating a migration to prevent interrupting the migration process. • Temporarily disable any antivirus software autoscans on the source machine to prevent interrupting the migration process.
d. e. 2. Choose the Windows migration type. Click Physical to ProLiant Migration (P2P), and then click Next. If you are performing a migration from Insight Control CMS, choose one of the following options: • To launch Insight Control using the Systems Insight Manager menu, select Deploy→Migration Tools→ Physical to ProLiant (P2P), and then follow the instructions to launch Insight Control Migration Tools. Insight Control server migration opens in a separate browser.
4. Select the volumes to be migrated. HP Insight Control server migration selects volumes marked as active by default. You cannot migrate or select unsupported file systems. You must migrate the boot partition. The boot partition is contained in an active volume. If only one active volume is detected by Insight Control server migration, the partition is required for migration and cannot be deselected. If multiple active volumes are detected, the active partitions will be selectable.
The Computed Destination Server Disk Requirement section lists the disks required on the destination server to support migrated volumes. Insight Control server migration updates the Size, Minimum Destination Size, and Maximum Destination Size values in the lower table dynamically as volumes in the upper table are selected or cleared for migration. A message appears under the table, indicating the number of logical units that you must create on the destination server.
Insight Control disables the Next and Previous buttons during the reboot. To view the booting process of the destination server, click Launch iLO, and then open the remote console. 6. 7. Test the network connections and latency between the source-to-destination server and the application-station-to-destination server. The results of a 2-second test initially appear. To perform additional tests, select a test time in the Test network connections section, and then click Test.
If you establish the source-to-destination or application-station-to-destination connection and the network test reports a transfer speed of at least 250 kb/s, the Next button is enabled. CAUTION: If the application-station-to-destination latency is less than 125 milliseconds, continue with the migration. Latency greater than 125 milliseconds might cause driver injection issues. 8. 9. 50 Click Next. Use the following steps to assign source disks to destination disks: 1.
Some of the columns and rows from the Assign Disks and Resize NTFS Volumes table include: • Minimum Destination Size—This column displays the minimum size that a partition or disk can be resized. • Destination Size—This column displays the actual size of the destination disk or partition. • Migration Overhead—This row displays the additional space that must be reserved on the destination disk to accommodate disk geometry differences.
10. Choose from the following options: • Select whether HP Insight Control server migration must perform disk-error checks on the source server before migration. By default, Insight Control server migration selects the Use CHKDSK to detect and fix errors on all source disks prior to migration checkbox. • Select the reboot action that the destination server must perform by choosing one of the following options: • Power off the destination server after migration is complete.
When you click Begin Migration, the migration agent performs a final network check. 13. Review the migration progress details.
14. To cancel the migration, click Cancel. After the entry in the Job Status field indicates you canceled the migration, reboot the source and destination servers. 15. Click Begin New Migration to start an additional migration. P2P post-migration tasks After you complete a P2P migration, perform the following steps on the destination server: 1. 2. 3. 4. 5. 6. 7. 8. 54 Log in with administrative rights. At each of the Welcome to the Found New Hardware wizard screens, click Cancel.
9. (Optional) Convert basic disks to dynamic disks. During migration, all dynamic disks are migrated to the destination server as basic disks. Therefore, if dynamic disks are preferred on the destination server, then basic disks can be manually converted back to dynamic disks. 10. Edit the boot.ini file, and update the boot entry with necessary switches. The /bootlog and /sos options can be removed.
NOTE: Bad blocks on Linux file systems are not supported by Insight Control. To verify that the source file systems do not have bad blocks, run file system-specific tools. Destination physical machine prerequisites • The primary storage controller must be configured with drives attached. • The destination server must be booted to Insight Control server migration Boot CD and running migration agent.
a. b. c. From the desktop, access the Insight Control Migration Wizard by clicking the Insight Control server migration application icon. On the Login page, enter your login credentials. From the Overview page, click the Migration Wizard tab. d. e. Choose the Linux migration type. Click Physical to ProLiant Migration (P2P), and then click Next.
2. 3. 4. 5. 6. 7. If you are performing a migration from Insight Control CMS, choose one of the following options: • To launch Insight Control using the Systems Insight Manager menu, select Deploy→Migration Tools→ Physical to ProLiant (P2P), and then follow the instructions to launch Insight Control Migration Tools. Insight Control server migration opens in a separate browser.
If swap is encrypted, you must manually create the swap partition on the destination server following migration. NOTE: You cannot migrate a partition acting as a Physical Volume (PV) for a Volume Group (VG). However, if you select a Logical Volume for migration in the Select Volumes To Be Migrated section, the required VG structure is created on the destination server. The Computed Destination Server Disk Requirement section lists the disks required on the destination server to support migrated volumes.
• 30 seconds • 60 seconds If you cannot establish the source-to-destination or application-station-to-destination connection, the Next button is disabled. Ensure that ports 51125 and 51126 are open between source and destination servers. If you establish the source-to-destination or application-station-to-destination connection but the network test reports a transfer speed below 250 kb/s, the Next button is disabled.
boot partition. Choose a “Destination Size” that is large enough to create the /-smpue files on the corresponding disk partition on the destination server. The Source Server requirement earlier in the document already state that 10 MB free spec must be available on /boot partition on the source. The recommended minimum value for the “Destination Size” for /boot is hence equal to the used space in /boot plus 10 MB. 3. 4.
• Migration Overhead—This row displays the additional space that must be reserved on the destination disk to accommodate disk geometry differences. • Disk 0, Disk 1, Disk2, and so on—For each row, the value in the Minimum Destination Size and Destination Size columns represent the sum of partition sizes and migration overhead space for the disk. 13.
When you click Begin Migration, the migration agent performs a final network check. 16. Review the migration progress details.
17. To cancel the migration, click Cancel. After the entry in the Job Status field indicates you canceled the migration, reboot the source and destination servers. 18. Click Begin New Migration to start an additional migration. P2P post-migration tasks After you complete a P2P migration, perform the following steps on the destination server: 1. 2. 3. 4. 5. 6. 64 Log in with administrative rights. Install the latest Linux ProLiant Support Pack (LSP). If necessary, verify the network connections.
Physical-to-virtual (P2V) migrations for Windows A P2V migration enables a source physical machine to be migrated to a virtual machine guest on a Microsoft Virtual Server, Microsoft Hyper-V, VMware, or HP integrated Citrix XenServer virtual machine host. Preparing for a P2V migration The following sections list prerequisites for a P2V migration. If you use a firewall, see the Configuring Insight Control with a firewall section in this guide.
d. e. 2. 3. If you are performing a migration from Insight Control CMS, choose one of the following options: • To launch Insight Control using the Systems Insight Manager menu, select Deploy→Migration Tools→ Physical to Virtual (P2V), and then follow the instructions to launch Insight Control Migration Tools. Insight Control server migration opens in a separate browser.
4. Select the volumes to be migrated. HP Insight Control server migration selects volumes marked as active by default. You cannot migrate or select unsupported file systems. You must migrate the boot partition. The boot partition is contained in an active volume. If only one active volume is detected by Insight Control server migration, the partition is required for migration and cannot be deselected. If multiple active volumes are detected, the active partitions will be selectable.
The Computed Destination Server Disk Requirement section lists the disks required on the destination server to support migrated volumes. Insight Control server migration updates the Size, Minimum Destination Size, and Maximum Destination Size values in the lower table dynamically as volumes in the upper table are selected or cleared for migration. A message appears under the table, indicating the number of logical units that you must create on the destination server.
The Virtual Machine Boot CD can be found at \webserver\webapps\smpui\smpbootcd-v-6.0.0.0.iso. The Virtual Machine Boot CD is also available in the SMP folder on the Insight Control server migration CD. For more information about manually booting a virtual machine using the Insight Control server migration Virtual Machine Boot CD, see Prerequisites for manually creating and booting a destination virtual machine.
Using Insight Control server migration to migrate servers
6. Specify the destination disk names, and then select the partitions to be resized in the Assign Disks and Resize NTFS Volumes table. By default, this page displays all selected disks as well as any mandatory disks such as primary partitions. Information displayed includes source disk, disk format, size, and destination disk information. The following screen appears when the manually booted destination is selected for virtual machine hosts.
If you are migrating to a virtual machine host that is automatically booted with the Insight Control server migration Virtual Machine Boot CD: a. b. c. 7. 8. Enter information in the Guest Display Name, Guest Memory, and Guest Storage Location boxes. Select the storage location (if applicable). To continue to the next step of the Migration Wizard, click Next. Test the network connections and latency between the source-to-destination server and the application-station-to-destination server.
If you establish the source-to-destination or application-station-to-destination connection and the network test reports a transfer speed of at least 250 kb/s, the Next button is enabled. CAUTION: If the application-station-to-destination latency is less than 125 milliseconds, continue with the migration. Latency greater than 125 milliseconds might cause driver injection issues. 9. Click Next. 10. Select the post-migration tasks, and then click Next.
11. Review and confirm the migration details, and then click Begin Migration.
When you click Begin Migration, the migration agent performs a final network check. 12. Review the migration progress details.
13. To cancel the migration, click Cancel. After the entry in the Job Status field indicates you canceled the migration, reboot the source and destination servers. 14. Click Begin New Migration to start an additional migration. P2V post-migration tasks After you complete a P2V migration, perform the following steps on the destination server: 1. 2. 3.
5. 6. 7. If applicable, then reassign drive letters of dynamic disk partitions using the disk manager to correspond with the original state. The virtual machine guest automatically detects new hardware and installs the required drivers. The mouse and keyboard might not be immediately active on the migrated virtual machine guest. Wait until all required drivers are automatically installed by the guest operating system, and reboot the migrated virtual machine guest when prompted.
• To install server migration Source Agent on the source server, verify that PermitRootLogin and PasswordAuthentication are set to yes in the /etc/sshd/sshd_config file, and then verify the sshd service is running. • For Linux migrations, GRUB Boot Loader is required as the primary boot loader on the source server. NOTE: Bad blocks on Linux file systems are not supported by Insight Control. To verify that the source file systems do not have bad blocks, run file system-specific tools.
d. e. 2. 3. Choose the Linux migration type. Click Physical to Virtual Migration (P2V), and then click Next. If you are performing a migration from Insight Control CMS, choose one of the following options: • To launch Insight Control using the Systems Insight Manager menu, select Deploy→Migration Tools→ Physical to Virtual (P2V), and then follow the instructions to launch Insight Control Migration Tools. Insight Control server migration opens in a separate browser.
4. Select the volumes to be migrated. HP Insight Control server migration selects volumes marked as active by default. You cannot migrate or select unsupported file systems. You must migrate the boot partition. The boot partition is contained in an active volume. If only one active volume is detected by Insight Control server migration, the partition is required for migration and cannot be deselected. If multiple active volumes are detected, the active partitions will be selectable.
The Computed Destination Server Disk Requirement section lists the disks required on the destination server to support migrated volumes. Insight Control server migration updates the Size, Minimum Destination Size, and Maximum Destination Size values in the lower table dynamically as volumes in the upper table are selected or cleared for migration. A message appears under the table, indicating the number of logical units that you must create on the destination server.
The Virtual Machine Boot CD can be found at \webserver\webapps\smpui\smpbootcd-v-6.0.0.0.iso. The Virtual Machine Boot CD is also available in the SMP folder on the Insight Control server migration CD. For more information about manually booting a virtual machine using the Insight Control server migration Virtual Machine Boot CD, see Prerequisites for manually creating and booting a destination virtual machine.
Physical-to-virtual (P2V) migrations for Linux 83
6. Specify the destination disk names, and then select the partitions to be resized in the Assign Disks and Resize NTFS Volumes table. By default, this page displays all selected disks as well as any mandatory disks such as primary partitions. Information displayed includes source disk, disk format, size, and destination disk information. The following screen appears when the manually booted destination is selected for virtual machine hosts.
If you are migrating to a virtual machine host that is automatically booted with the Insight Control server migration Virtual Machine Boot CD: a. b. c. 7. 8. Enter information in the Guest Display Name, Guest Memory, and Guest Storage Location boxes. Select the storage location (if applicable). To continue to the next step of the Migration Wizard, click Next. Test the network connections and latency between the source-to-destination server and the application-station-to-destination server.
If you establish the source-to-destination or application-station-to-destination connection but the network test reports a transfer speed below 250 kb/s, the Next button is disabled. If you establish the source-to-destination or application-station-to-destination connection and the network test reports a transfer speed of at least 250 kb/s, the Next button is enabled. CAUTION: If the application-station-to-destination latency is less than 125 milliseconds, continue with the migration.
11. Review and confirm the migration details, and then click Begin Migration.
When you click Begin Migration, the migration agent performs a final network check. 12. Review the migration progress details.
13. To cancel the migration, click Cancel. After the entry in the Job Status field indicates you canceled the migration, reboot the source and destination servers. 14. Click Begin New Migration to start an additional migration. P2V post-migration tasks After you complete a P2V migration, perform the following steps on the destination server: 1. 2. 3.
4. 5. View the event log on the destination server and disable any services or drivers that might have failed. The mouse and keyboard might not be immediately active on the migrated virtual machine guest. Wait until all required drivers are automatically installed by the guest operating system, and reboot the migrated virtual machine guest when prompted.
• Verify that a Windows NT boot loader (NTLDR) is installed. • During migration, the migration agent initiates an operating system reboot on the source physical machine. Verify that the operating system is on the first boot order. The Insight Control application supports migration of source physical machines that have operating systems installed on the primary drive (Hard Disk0) and the primary drive loaded first in the boot order.
d. e. 2. 3. If you are performing a migration from Insight Control CMS, choose one of the following options: • To launch Insight Control using the Systems Insight Manager menu, select Deploy→Migration Tools→ Virtual to ProLiant (V2P), and then follow the instructions to launch Insight Control Migration Tools. Insight Control server migration opens in a separate browser.
4. Select the volumes to be migrated. HP Insight Control server migration selects volumes marked as active by default. You cannot migrate or select unsupported file systems. You must migrate the boot partition. The boot partition is contained in an active volume. If only one active volume is detected by Insight Control server migration, the partition is required for migration and cannot be deselected. If multiple active volumes are detected, the active partitions will be selectable.
The Computed Destination Server Disk Requirement section lists the disks required on the destination server to support migrated volumes. Insight Control server migration updates the Size, Minimum Destination Size, and Maximum Destination Size values in the lower table dynamically as volumes in the upper table are selected or cleared for migration. A message appears under the table, indicating the number of logical units that you must create on the destination server.
6. Auto Boot - Let SMP boot the destination server—If you did not boot the destination server to the Insight Control server migration ProLiant Boot CD and you want Insight Control server migration to boot the system for you, select this option.
Insight Control disables the Next and Previous buttons during the reboot. To view the booting process of the destination server, click Launch iLO, and then open the remote console. To cancel the boot process and power down the destination server, click Cancel Booting. 7. 8. Test the network connections and latency between the source-to-destination server and the application-station-to-destination server. The results of a 2-second test initially appear.
If you establish the source-to-destination or application-station-to-destination connection and the network test reports a transfer speed of at least 250 kb/s, the Next button is enabled. CAUTION: If the application-station-to-destination latency is less than 125 milliseconds, continue with the migration. Latency greater than 125 milliseconds might cause driver injection issues. 9. Click Next. 10. Use the following steps to assign source disks to destination disks: 1. Map source disks to destination disks.
Some of the columns and rows from the Assign Disks and Resize NTFS Volumes table include: • Minimum Destination Size—This column displays the minimum size that a partition or disk can be resized. • Destination Size—This column displays the actual size of the destination disk or partition. • Migration Overhead—This row displays the additional space that must be reserved on the destination disk to accommodate disk geometry differences.
• If the destination server is selected to reboot upon completion, additional configuration options are available. If PSP executables are available on the application station and selected, the network settings on the destination can be configured. For information on how to upload PSP executables, see the Upload Drivers section. • Select a PSP to install on the destination server and configure a static IP for each destination NIC as needed.
When you click Begin Migration, the migration agent performs a final network check. 14. Review the migration progress details.
15. To cancel the migration, click Cancel. After the entry in the Job Status field indicates you canceled the migration, reboot the source and destination servers. 16. Click Begin New Migration to start an additional migration. V2P post-migration tasks After you complete a V2P migration, perform the following steps on the destination server: 1. 2. 3. 4. 5. 6. 7. 8. Remove the Insight Control server migration Boot CD from the CD drive of the physical machine, and then reboot the system.
[boot loader] default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS timeout=30 [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=”Windows Server 2003, Enterprise” /sos /bootlog /noexecute=optout /fastdetect multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=”HP Insight Control Preserved: Windows Server 2003, Enterprise” /userva=3030 /3gb /noexecute=optout /fastdetect 9. Install the ProLiant Support Pack either from the SmartStart CD included with your server or by accessing http://h18000.www1.hp.
Destination physical machine prerequisites • The primary storage controller must be configured with drives attached. • The destination server must be booted to Insight Control server migration Boot CD and running migration agent. Performing a V2P migration To start the V2P Migration Wizard: 1. If you are performing a migration from a stand-alone Insight Control application station: a. From the desktop, access the Insight Control Migration Wizard by clicking the Insight Control application icon. b.
3. 4. Select the volumes to be migrated. HP Insight Control server migration selects volumes marked as active by default. You cannot migrate or select unsupported file systems. You must migrate the boot, swap, usr, var, and root partitions. By default, Insight Control selects the active boot, swap, usr, var, and root partition on the specified source server for migration. You must select OS-critical file systems for migration. You can choose additional file systems for migration.
The Computed Destination Server Disk Requirement section lists the disks required on the destination server to support migrated volumes. Insight Control server migration updates the Size values in the lower table dynamically as volumes in the upper table are selected or cleared for migration. A message appears under the table, indicating the number of logical units that you must create on the destination server. Additional space might be required to accommodate disk geometry differences.
6. Auto Boot - Let SMP boot the destination server—If you did not boot the destination server to the Insight Control server migration ProLiant Boot CD and you want Insight Control server migration to boot the system for you, select this option.
Insight Control disables the Next and Previous buttons during the reboot. To view the booting process of the destination server, click Launch iLO, and then open the remote console. To cancel the boot process and power down the destination server, click Cancel Booting, then click Next. 7. 8. Test the network connections and latency between the source-to-destination server and the application-station-to-destination server. The results of a 2-second test initially appear.
If you establish the source-to-destination or application-station-to-destination connection and the network test reports a transfer speed of at least 250 kb/s, the Next button is enabled. CAUTION: If the application-station-to-destination latency is less than 125 milliseconds, continue with the migration. Latency greater than 125 milliseconds might cause driver injection issues. 9. Click Next. 10. Use the following steps to assign source disks to destination disks: 1. Map source disks to destination disks.
Some of the columns and rows from the Assign Disks table include: • Minimum Destination Size—This column displays the minimum size that a partition or disk can be resized. • Destination Size—This column displays the actual size of the destination disk or partition. • Migration Overhead—This row displays the additional space that must be reserved on the destination disk to accommodate disk geometry differences.
12. Click Next. 13. Review and confirm the migration details, and then click Begin Migration.
When you click Begin Migration, the migration agent performs a final network check. 14. Review the migration progress details. 15. To cancel the migration, click Cancel. After the entry in the Job Status field indicates you canceled the migration, reboot the source and destination servers. 16. Click Begin New Migration to start an additional migration. V2P post-migration tasks After you complete a P2P migration, perform the following steps on the destination server: 1. 2. 3. 4. 5. 6.
Preparing for a V2V migration The following sections list prerequisites for a V2V migration. If you use a firewall, see the Configuring Insight Control with a firewall section in this guide. Source physical machine prerequisites • The following disk types are not supported for migration. You must manually migrate these disks after server migration.
Destination virtual machine host or virtual machine prerequisites The following prerequisites are for target virtual machine hosts in a P2V migration: • Select one of the following: • Let Insight Control create the virtual machine automatically, and then boot it using the Insight Control server migration Virtual Machine Boot CD for virtual machines. • Create the virtual machine manually, and then boot the virtual machine manually using the Insight Control server migration Virtual Machine Boot CD.
d. e. 2. 3. If you are performing a migration from Insight Control CMS, choose one of the following options: • To launch Insight Control using the Systems Insight Manager menu, select Deploy→Migration Tools→ Virtual to Virtual (V2V), and then follow the instructions to launch Insight Control Migration Tools. Insight Control server migration opens in a separate browser.
contained in other active volumes, but the partitions do not need to be migrated. The operating system must be stored on the boot disk and loaded using NT Boot Loader (NTLDR). Volumes on dynamic disks are migrated to partitions on basic disks. Volumes that span multiple dynamic disks (including spanned, striped, mirrored, and RAID 5 volumes) are migrated to a single contiguous partition. Volumes stored on a common source disk must also be stored on a common destination disk.
• 116 If the destination virtual machine is not created and you want Insight Control server migration to automatically create the destination VM: 1. Select Auto Boot - Automatically have VM created through SMP wizard. 2. Add the login credentials (username and password) for the VM Host. 3. Enter the four-part VM Pre-boot IP address, Subnet Mask, and Gateway (optional) to be assigned to the virtual machine. 4. Click Next.
Virtual-to-virtual (V2V) migrations for Windows 117
6. By default, this page displays all selected disks as well as any mandatory disks such as primary partitions. Information displayed includes source disk, disk format, size, and destination disk information. The following screen appears when the manually booted destination is selected for virtual machine hosts. The following screen appears when the automatically booted destination is selected for virtual machine hosts.
If you are migrating to a virtual machine host that is automatically booted with the Insight Control server migration Virtual Machine Boot CD: a. b. c. 7. 8. Enter information in the Guest Display Name, Guest Memory, and Guest Storage Location boxes. Select the storage location (if applicable). To continue to the next step of the Migration Wizard, click Next. Test the network connections and latency between the source-to-destination server and the application-station-to-destination server.
If you establish the source-to-destination or application-station-to-destination connection and the network test reports a transfer speed of at least 250 kb/s, the Next button is enabled. CAUTION: If the application-station-to-destination latency is less than 125 milliseconds, continue with the migration. Latency greater than 125 milliseconds might cause driver injection issues. 9. Click Next. 10. Select the post-migration tasks, and then click Next.
11. Review and confirm the migration details, and then click Begin Migration.
When you click Begin Migration, the migration agent performs a final network check. 12. Review the migration progress details.
13. To cancel the migration, click Cancel. After the entry in the Job Status field indicates you canceled the migration, reboot the source and destination servers. 14. Click Begin New Migration to start an additional migration. V2V post-migration tasks After you complete a V2V migration, perform the following steps on the destination server: 1. 2. 3.
Preparing for a V2V migration The following sections list prerequisites for a V2V migration. If you use a firewall, see the Configuring Insight Control with a firewall section in this guide. Performing a V2V migration To start the V2V Migration Wizard: 1. 124 If you are performing a migration from a stand-alone Insight Control application station: a. From the desktop, access the Insight Control Migration Wizard by clicking the Insight Control application icon. b.
d. e. 2. 3. 4. Choose the Linux migration type. Click Virtual to Virtual Migration (V2V), and then click Next. If you are performing a migration from Insight Control CMS, choose one of the following options: • To launch Insight Control using the Systems Insight Manager menu, select Deploy→Migration Tools→ Virtual to Virtual (V2V), and then follow the instructions to launch Insight Control Migration Tools. Insight Control server migration opens in a separate browser.
The Computed Destination Server Disk Requirement section lists the disks required on the destination server to support migrated volumes. Insight Control server migration updates the Size values in the lower table dynamically as volumes in the upper table are selected or cleared for migration. A message appears under the table, indicating the number of logical units that you must create on the destination server. Additional space might be required to accommodate disk geometry differences.
auto boot option. Therefore, HP recommends booting the destination server from the application station using the auto boot option. • 6. If the destination virtual machine is not created and you want Insight Control server migration to automatically create the destination VM: 1. Select Auto Boot - Automatically have VM created through SMP wizard. 2. Add the login credentials (username and password) for the VM Host. 3.
7. 8. Test the network connections and latency between the source-to-destination server and the application-station-to-destination server. The results of a 2-second test initially appear. To perform additional tests, select a test time in the Test network connections section, and then click Test.
10. Select the post-migration tasks, and then click Next.
in step 3 of the Migration Wizard. After the migration is completed, manually reboot the destination virtual machine. ▲ Select whether the Insight Control application must perform disk-error checks on the source server before migration. By default, the Use CHKDSK to detect and fix errors on all source disks prior to migration checkbox is selected. 11. Review and confirm the migration details, and then click Begin Migration.
When you click Begin Migration, the migration agent performs a final network check. 12. Review the migration progress details.
13. To cancel the migration, click Cancel. After the entry in the Job Status field indicates you canceled the migration, reboot the source and destination servers. 14. Click Begin New Migration to start an additional migration. SAN migrations IMPORTANT: SAN migrations are not supported for Linux migrations. Insight Control supports Windows P2P and V2P migrations to servers with Fibre Channel SAN connectivity. To verify that your Fibre Channel HBA is supported, see the Insight Control Support Matrix.
can be used for configuring HP StorageWorks 4100/6100/8100 EVAs, you must verify that the logical units have been presented to the HBA of the destination server. • Configuration of SAN switches. Intermediate SAN switches used between the destination server and the storage must be configured for appropriate zoning to ensure proper visibility between the destination server and the storage array. • Configuration of the HBA BIOS.
An option also exists to have the Systems Insight Manager-detected hosts always display with no additional steps required. By default, to have the appropriate hosts always listed on each necessary step of the Migration Wizard: 1. Launch Insight Control from Systems Insight Manager. Select Deploy→SMP Migration Tools→Type of Migration, and then select a migration option. You can also select a source virtual machine or source server, and then select a migration option using Quick Launch. 2. 3.
4. Select the Display servers Discovered in SIM checkbox. If Systems Insight Manager has a large number of systems discovered, then it might take additional time to load each Migration Wizard step requiring host list. The systems detected in Systems Insight Manager are filtered in the Show Host List to display the proper system type for each action.
• 136 If the selected server or virtual machine 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 Insight Control server migration application Migration Wizard.
4. 5. If a different host needs to be selected, then click Show Host List. All selected hosts discovered in Systems Insight Manager are displayed. If not, then follow the necessary steps to continue to step 2 and 3 of the Migration Wizard. The Show Host List option also appears in step 3 of the Migration Wizard. The proper IP address of the destination virtual machine host or physical server can be added, or a server from the Show Host List can be selected.
• 138 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 machine or source server.
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 migration, then the Quick Launch list does not display the unsupported migration options.
6 Viewing migration logs You can view job-specific log files on the application station by accessing HP Insight Control server migration installation path\logs. You can also view job-specific log files by clicking the View logs link in the Progress column on the View Status/Logs page. When a job is complete, its link no longer appears in the View Status/Logs page, but the job-specific log files are still available in the Insight Control server migration installation path\logs directory.
To view migration logs, scroll through the View Migration Result Log table. This table includes the following columns: • Checkbox—Enables you to select migration logs for deletion. You can select multiple logs simultaneously. Select the logs to be deleted, and then click Delete. • Status—Displays icons that show if a migration was successful, failed, or has information. • Time—Lists the date and time of the migration step. • Server—Indicates where the migration step was performed.
7 Uploading drivers The Upload Drivers tab displays the status of iSCSI initiator installed and all PSPs added to the application station for HP Insight Control server migration. PSPs executables can be uploaded from this console when Insight Control is launched as a standalone product or when Insight Control is launched from Systems Insight Manager. Enter the PSP location in the box, or click Browse to find the PSP file location, and then click Upload.
8 Troubleshooting Installation When launching the HP Insight Control server migration wizard immediately after installation, the message Unable to communicate with the HP Insight Control server migration service appears on the wizard page Usually, the service manager shows that HP Insight Control server migration service is launched. However, because of DNS lookup or other network latency, the communication to the service is not established, which causes this error message.
Support for older versions of standalone P2P application The installation of standalone P2P application (version 1.4 and earlier) on a system which already has Insight Control is not supported. If you need to downgrade to an older version of the P2P application, you must use the following installation order: 1. 2. Uninstall the older version of P2P application. Install Insight Control.
Verify that necessary ports are open on the application station, source servers (physical or virtual) and destination servers (physical or virtual machines or virtual machine hosts). 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 Static certificates are used when you install the server migration Source Agent manually on the source or destination server.
NOTE: This agent does not detect whether the corrective action has been performed. Subsequent attempts to execute this agent indicate that the corrective action is required. The corrective action only has to be applied once. To resolve this issue: 1. 2. 3. Cancel the migration agent execution. In the command prompt window, change to the root directory of the Windows disk. Run the following command: SFC /SCANNOW. This command might take several minutes.
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 User Guide. Verify that the source server can be reached from the application station.
partitions appear as RAW partitions in the Migration Wizard, and data might be incomplete after the migration. You must deselect LUNs initialized with GPTs in step 2 of the Migration Wizard, and manually copy data on GPT disks after the migration.
IP address configuration fails on a manually booted virtual machine in Microsoft Hyper-V for a P2V or a V2V migration If you have manually created the virtual machine on Microsoft Hyper-V for a P2V or a V2V migration, booted the virtual machine manually with the Insight Control server migration Virtual Machine Boot CD for virtual machines, and you are unable to configure an IP address on the virtual machine, then perform the following: • Ensure that the virtual machine that you have manually created has a
Insight Control server migration Boot CD might stop responding when exiting the Array Configuration Utility When exiting the Array Configuration Utility, the Insight Control server migration Boot CD might stop responding. If this occurs, to restart the server, physically restart the server or use the Virtual power option in remote management.
You can view a list of IP addresses where virtual media is still connected to the server in the Insight Control server migration installation directory/bin/iLOIP.lst file. To disconnect these virtual media, access Insight Control server migration installation directory/bin/ResetILOVM.cmd and enter -i xxx.xxx.xxx.xxx -u username -p password where xxx.xxx.xxx.xxx is the remote management IP address.
• Reboot the destination server to ROM-Based Setup Utility (RBSU) by pressing the F9 key during Power-On Self-Test (POST). • Select the Boot Controller Order option and verify the proper boot order for the storage controllers. • Press ESC to exit RBSU, and then press F10 to confirm the exit and to save the changes. • Reboot the destination server using the SMP Boot CD. • When the destination server boots up, the SMP Boot CD will detect the storage controller.
Migration fails with the error The File System on Source Disk \\.\PhysicalDrive0, Partition 0 Could Not Be Resized During the Migration Migration might fails with the error The file system on source disk \\.\PhysicalDrive0, partition 0 could not be resized during the migration in the logs.
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. You must manually power off the VM after the migration is complete.
To resolve this issue, when Windows boots up, press F8 to go to boot options and select Last known good configuration. After Windows fully boots up, uninstall the "HP StorageWorks Tape Drivers for Windows" drivers and reboot the server. SAN-connected destination server displays blue screen To migrate Windows Server 2003 to a SAN-connected destination server, you must first install Service Pack 1, Service Pack 2, and the updated Storport storage driver (see http://support.microsoft.
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.
1. 2. 3. 4. 5. 6. 7. Restart the destination server. Press F8 when you see the following message: Please select the operating system to start. When the Windows Advanced Options menu appears, select Last Known Good Configuration (your most recent settings that worked), and then press Enter. After Windows boots, install the ProLiant Support Pack on the destination server manually. Do not restart the server immediately. The driver for the Emulex HBA now needs to be updated. a.
Mouse does not work on the destination server's iLO after a Linux X2P migration The mouse does not work on the destination server's iLO after a Linux X2P migration. To resolve this issue, deselect High performance mouse mode on the remote console of destination server iLO. USB Mouse or Keyboard Drivers Not Loaded After a X2P Windows Migration After a successful Windows migration, the mouse and keyboard drivers may not be loaded. As a result, the mouse and keyboard do not work on the destination server.
6. 7. Install the latest PSP on the destination server. Remove the (dongle-attached) USB mice and keyboards from the source and the destination servers. 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. To resolve this issue, use the following procedure: 1. 2. 3. 4. Log in to the destination server using the keyboard.
Virtual machine hosts Integrated Components do not install on the destination virtual machine following migration To resolve this issue: 1. 2. 3. Power down the destination virtual machine. Add a CD-ROM drive to the virtual machine. Power up the virtual machine, and then restart the installation of the Integrated Components.
9 Support and other resources Contacting HP Information to collect before contacting HP Be sure to have the following information available before you call 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, se
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 Control Management, HP Systems Insight Manager, and ProLiant Essentials products. HP worldwide customer service contact numbers HP worldwide customer service contact numbers are available at the following website: http://welcome.hp.com/country/us/en/wwcontact_us.
A Portable Images Network Tool (PINT) The Portable Images Network Tool (PINT) automates NIC configuration on the servers after moves. NOTE: For more information on PINT, see the PINT readme files at system drive\Program Files\HP\HP Insight Control server migration\PI\PINT. PINT can only be used with servers supported by Insight Control server migration. For more information, see the Insight Control Support Matrix.
Glossary CMS Central Management Server. full duplex Full duplex is the capability to send data in both directions at the same time. guest operating system A reference to a distinct operating system instance running in a virtual machine. host operating system A reference to the operating system that is the foundation for a virtual machine.
Index A D accessing System page, 43 adding license keys, 41 antivirus software, 15 application preparation, critical or hardware-dependent, 13 application station memory and CPU resources, 13 overview, 11 uninstalling, 162 auto booting destination server fails troubleshooting, 152 deploying migration agents, 23 using Insight Control CMS, 23 deployment fails, 149 destination preparation troubleshooting, 150 destination server booting for P2P, 29 booting for V2P, 29 booting for X2V, 29 booting using Insigh
feedback email address for documentation, 164 firewalls, 14, 146 LSP using with Insight Control, 16 H memory and CPU resources on the application station, 13 menus missing in Insight Control, 145 Microsoft DNS Server does not map the host name to DHCP-generated IP addresses, 147 Microsoft Small Business Server, 14 migration agent restarting, 29 migration process troubleshooting, 154 Migration Wizard page, 44 using to boot a destination server, 29 using to boot a virtual machine, 32 using to create a virt
resizing volumes for Windows migration, 15 O OpenSSH requirements, 17 operating system support, 12 overview application station, 11 configuration for Insight Control, 17 destination server, 11 Insight Control, 11 installation for Insight Control application, 17 source server, 11 Overview screen, 36 P P2P (see physical-to-ProLiant) P2V (see physical-to-virtual) performing P2P migrations, 45 P2V migrations, 65, 78 V2P migrations, 91, 103 V2V migrations, 113, 124 physical destination servers, 18 physical-to-
server migration Source Agent fails to launch when rebooting in migration agent mode, 156 unrecoverable sector-read errors on hard drive not supported and fail a P2P migration, 156 unrecoverable sector-read errors on hard drive not supported and fail a P2V migration, 156 source servers, 17, 18 station service port number, changing, 22 storage controllers appears as unknown, 152 support, 142 support service, 163 System page accessing, 43 overview, 43 Systems Insight Manager requirements, 17 mouse stops work
prerequisites for P2V migration destination, 65, 78, 113 requirements, 18 virtual-to-ProLiant migration overview, 90, 102 migration prerequisites, 90, 102 migrations, 90, 91, 102, 103 post-migration configuration tasks, 101, 111 virtual-to-virtual migrations, 111, 112, 113, 123, 124 post-migration configuration tasks, 123 troubleshooting, 155 virus scans, 15 volumes resizing NTFS for Windows migration, 15 VSE documentation, 164 W warranty information, 164 websites HP authorized resellers, 164 HP technical
