HP Insight Server Migration software for ProLiant 3.70 Release Notes HP Part Number: 484316-004 Published: April 2009 © Copyright 2007, 2009 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. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments Microsoft, Hyper-V, Windows, Windows Server, and Windows XP are U.S. registered trademarks of Microsoft Corporation. Intel is a registered trademark of Intel Corporation in the United States and other countries. VMware, VMotion, and Virtual SMP are trademarks of VMware Inc. Table of Contents Related documents.........................................................................................5 1 3.70 Release Notes....................................................................................7 Version.................................................................................................................................................7 What's new in version 3.70.....................................................................................................................7 Supported platforms...............................................................................................................................7 Installation notes....................................................................................................................................7 Limitations and known issues in version 3.70..............................................................................................7 2 HP contact information..............................................................................11 Table of Contents 3 4 Related documents For more information, see the following resources: • http://www.hp.com/go/migrate • HP Insight Server Migration software for ProLiant User Guide • HP Insight Server Migration software for ProLiant Support Matrix • Portable Images Network Tool (PINT) readme files 5 6 1 3.70 Release Notes These release notes indicate the changes that have occurred since the last release of SMP. Version HP Insight Server Migration software for ProLiant 3.70 Release Notes What's new in version 3.70 • Added new hardware support. For more information, see the SMP 3.70 Support Matrixon the SMP Boot CD. • Added support for migrating the Red Hat Enterprise Linux (RHEL) 5.2 Operating System. For more information, see the HP Insight Server Migration software for ProLiant Support Matrix. Supported platforms For more information about supported platforms and system prerequisites, see the SMP Support Matrixon the SMP Boot CD. Installation notes Microsoft® iSCSI Software Initiator Version 2.06, 2.07, or 2.08 must be installed on the SMP application station. Other versions of the initiator, including later versions, cannot be used with this version of the SMP application. To download iSCSI Software Initiator Version 2.06, 2.07, or 2.08 search for “iSCSI 2.06”, “iSCSI 2.07”, or “iSCSI 2.08” at http://www.microsoft.com. The white paper, Performing Physical to ProLiant application migrations with the HP Insight Server Migration software for ProLiant – Physical to ProLiant Edition, describes how to perform physical to ProLiant application migrations and provides information about configuring domain controller and exchange servers. This white paper is available through your HP account manager. The SMP User Guidedescribes how to perform the supported migrations and the required prerequisites. Limitations and known issues in version 3.70 • The mouse might stop working on the destination ESX virtual machine after a V2V migration. To resolve this issue, use the following procedure: 1. Log in to the destination server using the keyboard. 2. Navigate to the Device Manager by right-clicking My Computer and selecting Manage. 3. Right-click VMWare Pointing device and select Uninstall. The VMWare Pointing Device entry disappears from the list of devices. 4. Choose to Scan for hardware changes. A PS/2 compatible mouse appears in the Device Manager. 5. Reboot the virtual machine. • The network adapter in the destination ESX virtual machine might not be initialized after a V2V migration. To resolve this issue, use the following procedure: 1. Log in to the destination server using the keyboard. 2. Navigate to the Device Manager by right-clicking My Computer and selecting Manage. 3. Right-click VMWare Accelerated AMD PCNet Adapter and select Uninstall. The VMWare Accelerated AMD PCNet Adapter entry disappears from the list of devices. 4. Choose to Scan for hardware changes. A valid virtual network adapter appears in the Device Manager. 5. Reboot the virtual machine. Version 7 • Linux migrations using SMP might fail if there are no valid entries in the GRUB device mapping file for all the valid boot devices listed in the Grand Unified Bootloader (GRUB) configuration file. GRUB refers to the first hard disk as /dev/hd0 rather than using conventional Linux device names such as /dev/hda. GRUB maintains its disk device names and the corresponding Linux device names in a GRUB device mapping file (/boot/grub/device.map). For example, the device.map file might look like the following when the system has to boot the IDE devices before the SCSI devices: (hd0) /dev/hda (hd1) /dev/hdb (hd2) /dev/sda (hd3) /dev/sdb The "root" line in the GRUB configuration file (/etc/grub.conf) specifies the boot device and is usually in the form root (hd0,1). To successfully perform a Linux migration, verify that there are valid entries in the GRUB device mapping file for all the valid boot devices listed in the GRUB configuration file. GRUB tools may have to be used to ensure this consistency before initiating a migration through SMP. Extensive information about GRUB is available at http://www.gnu.org/software/grub/. • Migrations of a Linux server with Logical Volume Manager (LVM) logical volumes might fail if the destination server is not a bare metal server and the destination disks have been partitioned prior to migration. Because of the existing partitions, SMP does not re-partition the destination disks. This causes a migration failure if there is insufficient space to create a new partition to ensure successful LVM migration. In such cases, verify that the pre-existing partitions on the destination disks are deleted before initiating a migration. The fdisk tool can be used to delete the partitions. • If the error Failed: Drivers could not be injected into boot disk... displays and the iSCSI mounting error The target has already been logged in via an iSCSI session appears in the log files, restart the application station and retry the migration. • During X2P migrations, if the automatic booting option was chosen during the "Identify Destination Server" step of the Migration Wizard and if the destination server does not boot, then either of the following scenarios might occur: • Automatic booting fails with the error Could not get timely response from iLO. 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. In either scenario, reset the iLO on the destination server and then reboot the destination server. • During Linux migrations, SMP does not support encrypted file system migrations. If there are any encrypted file systems on the source server, then they will be displayed as raw partition or raw logical volume in Step 2 ("Select Volumes to Migrate"). Raw partitions and raw logical volumes cannot be chosen for migrations. If a migration is required for these types of systems, enter the password for the encrypted file system on the source server console when the source server boots into exclusive mode. • During X2P migrations, the destination server might fail to boot while loading initrd.img. This can happen when the destination server is booted either by connecting the ProLiant Boot CD through iLO Virtual Media or by choosing the Auto Boot option in the Migration Wizard. To resolve this issue, insert the SMP Physical Boot CD in the DVD drive of the destination server and then reboot the destination server. • SMP cannot deploy agents to a server which has only IPv6 addresses. Verify that the destination server has at least one IPv4 address. • If the SMP ProLiant Boot CD cannot detect the primary storage controller, you may need to reconfigure the storage controller environment variable. 1. Reboot the destination server to Rom-Based Setup Utility (RBSU) by pressing the F9 key during POST. 2. Select the Boot Controller Order option and verify the proper boot order for the storage controllers. 8 3.70 Release Notes 3. Press Esc to exit RBSU, and then press F10 to confirm the exit and to save your changes. 4. Reboot the destination server using the SMP ProLiant Boot CD. When the destination server boots up, the SMP ProLiant Boot CD will detect the storage controller. • The NC375i embedded NIC is not supported by SMP. To initiate a migration to a destination server with the NC375i embedded NIC, install an optional NIC on the destination server and initiate the migration process. • SMP might stop responding during auto-booting of a Hyper-V VM for an X2V migration. To resolve this, ensure the following: • File-sharing is enabled on the application station and the Hyper-V host. • The Server or Workstation service is started on the application station and the Hyper-V host. • A "Client for Microsoft Networks" client is added to the network interface properties on the application station and on the Hyper-V host. • Before migrating a source server with BitLocker Drive Encryption enabled and drives encrypted using BitLocker, decrypt the drives on the source server and disable BitLocker. • If a migration to an ML310 G5p server fails during disk cloning, perform the following actions to resolve the issue: 1. Reboot the destination server and press F9 to enter the BIOS settings of the destination server. 2. Go to Advanced Options and select Erase Boot Disk. 3. Rerun the migration process. • Partitions cannot be resized for P2V or V2V migrations to an agent-based virtual machine host from a Windows 2008 application station. • Deploying SMP Agent from the application station to a source server running a Spanish language Operating System might fail if the source NIC used for the agent deployment has IPv6 enabled. To resolve this issue, disable the IPv6 configuration on the source server NIC or manually deploy the agent to the source server. • The mouse and keyboard might not work after migrating a Hyper-V virtual machine to a ProLiant server. To resolve this issue, reboot the destination server. • The certificates deployed on the SMP application station and with SMP Agents are packaged along with SMP. • The application station fails to connect to the destination server when the server is auto-booted for a P2P or V2P migration, even though the destination server boots up and the agent starts up. This might happen if the destination server has multiple NICs connected to different networks and the IP address gets configured to a NIC which is not on the same network as the application station. To resolve this issue, manually boot the destination server, and then manually assign the IP address to the NIC, which is on the same network as the application. • Migrations to HP integrated Citrix XenServer require a manual shutdown of the destination virtual machine following the migration. To ensure the destination virtual machine does not reboot to the SMP VM Boot CD, adjust the boot order to Hard Disk before DVD-drive before rebooting. • If the server becomes unresponsive during PSP installation, reboot the server, and then reinstall PSP. • For some virtual machines running on VMware ESX 2.5. xhosts, the source agent user interface might not appear when the agent launches. Although the agent does not appear, it is running in a command window, and you can still initiate migration. • If you see an error similar to Setup cannot copy the atiiiexx.dll, then to continue installing PSP, click Cancel. • While launching a migration from HP SIM, verify that the source server is properly discovered with an IP address and operating system type. • SMP–X2X subscription licenses are not blocked from being added to the HP SIM License Manager. However, adding SMP licenses to the HP SIM License Manager is not supported. To perform the migration using the license, from the License tab in SMP, you add the license again. • If an HTTP error appears on the SMP Migration Wizard, to refresh the browser, perform the following steps: Limitations and known issues in version 3.70 9 1. Close the browser running SMP application. 2. Restart the SMP Web and Application services. 3. In a new browser, launch the SMP application. • Number of processors, memory, storage space, and operating system information appearing in the Migration Wizard might not always appear correctly. This incorrect display of server details does not affect migration. • Sorting within the Show Host List table by IP address might not sort items in the correct order. The Show Host List button appears in steps 1 and 3 of Migration Wizards and on the Deploy Agent tab when launched from HP SIM. • SMP does not support migration to a destination server with unsupported network adapters or storage controllers installed. Additional unsupported hardware in the destination server might cause issues. Before beginning a migration, remove all unsupported hardware from the destination server. For a complete list of supported options, see the SMP Support Matrix.Upon completion of a migration, hardware can be added to the destination server. • The SMP application converts dynamic volumes to basic partitions during migration. Because basic partitions can be no larger than one sector less than 2 TB: • Dynamic volumes 2 TB or larger cannot be migrated using the SMP application. • Volumes can be resized to a maximum size of less than 2 TB. • LUNs initialized with GUID partition tables (GPT) are not supported, even if they contain NTFS partitions. Those partitions appear as RAW in the Migration Wizard, and data might be incomplete after the migration. Data on GPT disks can be copied manually after the migration. • Partitions created with third-party partitioning tools such as Gnome might not show the proper file system type in the SMP application. This does not affect migration. • If the logical disks are not recognized in the list of the Destination Disk box in step 5 of the Migration Wizard, then perform the following actions: 1. Verify the storage controller is supported. For hardware support, see the SMP Support Matrix located on the SMP Boot CD. 2. Verify the primary controller has the latest firmware updates. You can download the latest firmware updates from http://www.hp.com. • The SMP application station requires a minimum of 600 MB of free memory for SMP migrations. If an Out of memory error occurs on the application station during migration, then free memory or add memory to the application station and restart the migration. • When exiting the Array Configuration Utility, the SMP Boot CD might stop responding. If this occurs, physically restart the server or use the Virtual Power option in iLO. • The destination server might display a blank screen when booting to the SMP Boot CD if the server has more than 64 GB of RAM. To resolve this issue: 1. At the boot menu, press ESC to enter text mode. 2. At the text mode boot prompt, type sos mem=4G. 3. Press Enter. 10 3.70 Release Notes 2 HP contact information For more information about SMP: • http://www.hp.com/go/migrate • HP Insight Server Migration software for ProLiant User Guide • HP Insight Server Migration software for ProLiant Support Matrix For the name of the nearest HP authorized reseller: • In the United States, see the HP US service locator at http://www.hp.com/service_locator. • In other locations, see Contact HP worldwide at http://welcome.hp.com/country/us/en/wwcontact.html. For HP technical support: • In the United States, for contact options see Contact HP United States at http://welcome.hp.com/ country/us/en/wwcontact.html. To contact HP by phone, call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored. • In other locations, see Contact HP worldwide at http://welcome.hp.com/country/us/en/wwcontact.html. 11