Page 1: User Guide
HP Insight Server Migration software for ProLiant User Guide HP Part Number: 461487-004 Published: April 2009 Edition: 3.70...
Page 2 © 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.21 1 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.
Page 3: Table Of Contents
Table of Contents About this document..................11 Document organization..........................11 New and changed information in this edition...................11 Related documents..........................11 1 Introduction.....................13 HP Insight Server Migration software for ProLiant..................13 SMP benefits............................13 SMP platform support..........................13 SMP components..........................13 Planning a migration strategy.........................13 Upgrading to SMP from SMP or P2P....................13 Downgrading to SMP or P2P from SMP....................14 Hardware and operating system support.....................14 Configuration planning........................14...
Page 4 Deploying SMP Agent through the HP SIM CMS menu if SMP and HP SIM 5.3 are installed....29 Deploying SMP Agent through the HP SIM CMS Quick Launch feature..........30 Using the application station to deploy SMP Agent................30 Deploying SMP Agent using the Deploy Agent tab of the wizard on the application station....30 Deploying SMP Source Agent directly from the Migration Wizard on the application station....31 Manually running SMP Source Agent on the source server..............31 Deploying Windows SMP Source Agent locally on the source server..........31...
Page 5 SMP application station prerequisites....................81 Destination virtual machine host or virtual machine prerequisites............82 Performing a V2V migration......................82 V2V post-migration tasks........................92 Virtual-to-ProLiant (V2P) migrations......................93 Preparing for a V2P migration......................93 Source physical machine prerequisites...................93 SMP application station prerequisites....................94 Destination physical machine prerequisites..................94 Performing a V2P migration......................94 V2P post-migration tasks.........................102 SAN migrations..........................103 SMP application integration to HP SIM....................104...
Page 6 IP address configuration fails on a manually booted virtual machine in Hyper-V for a P2V or a V2V migration..........................126 Kernel Panic when booting a virtual machine to the SMP Virtual Boot CD.........126 Manual boot of HP integrated Citrix XenServer fails..............126 Mouse does not work on a virtual machine booted with the SMP VM Boot CD for virtual machines..127 Primary array controller does not have logical drives defined............127 Primary controller configured in the system does not have drives attached........127...
Page 7 HP contact information.........................138 A Portable Images Network Tool (PINT)............139 Glossary....................141 Index.......................143 Table of Contents...
Page 9 List of Tables 1- 1 Related HP products for extending deployment..................18 3- 1 Server and agent type........................29 Restarting SMP Agents on source and destination servers..............35 5- 1 Concurrent and queued migrations....................48 Unsupported disk types........................93 Unsupported disk types........................93 SMP Steps and HP SIM system filters applied..................106 6- 1 Job-specific log files and job names....................117 8- 1...
Page 11: About This Document
About this document Document organization This User Guide consists of chapters to help introduce you to SMP Edition, the installation and configuration requirements, how to install and configure SMP, troubleshooting items, followed by HP contact information, a glossary, and index. New and changed information in this edition For information on what's new or has changed in this document since its previous release, see the SMP Release Notes .
Page 13: Introduction
1 Introduction HP Insight Server Migration software for ProLiant HP Insight Server Migration software for ProLiant (SMP) simplifies the server consolidation process. SMP migrations involve moving an operating system, applications, and data from one server to another, instead of manually redeploying these elements on a new server. SMP allows you to migrate Windows and Linux operating systems to new compatible hardware.
Page 14: Downgrading To Smp Or P2P From Smp
If you are upgrading from a previous version of SMP—P2P 1. x, then all remaining licenses within SMP—P2P 1. x are detected, upgraded, and included in the SMP application. This includes Flexible Quantity, Demo, and Subscription licenses. The licenses retain their product name in SMP; however, they are still available for any P2P or V2P migrations.
Page 15: Schedule Preparation
IMPORTANT: Servers with Windows Original Equipment Manufacturer (OEM) licenses are not supported for migration. For licensing questions, contact HP support. Schedule preparation Schedule preparation is essential when planning a migration strategy. Be sure to include adequate time for copying data. Large volumes take time to migrate. Under optimal conditions, an SMP migration requires two to three minutes to migrate 1 GB of data.
Page 16: Microsoft Small Business Server
The migration runs in Directory Services Restore Mode instead of booting into SMP Agent Mode. As a result, CHKDSK does not run before the migration of domain controllers. For more information about preparing a migration of domain controllers, see your HP account manager for the white paper Performing physical to ProLiant application migrations with the HP Insight Server Migration software for ProLiant –...
Page 17: Antivirus Software
NOTE: SMP 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.
Page 18: File System Selection For A Linux Source Server
File system selection for a Linux source server Bad blocks on Linux file systems are not supported by SMP. To ensure that the source file system does not have bad blocks, run file system-specific tools. Resize is not supported for Linux file systems. ProLiant Support Pack IMPORTANT: The information in this section applies only to P2P or V2P migrations.
Page 19: Smp Installation And Configuration Requirements
2 SMP installation and configuration requirements This chapter lists the hardware and software required for each component in the SMP environment. The SMP environment consists of the following components: Microsoft Windows-based application station Physical or virtual source server Physical or virtual destination server Destination virtual machine host (for P2V and V2V only) HP SMP application station and HP SIM Central Management Server (CMS) The application station requires the following components to be installed:...
Page 20: Windows Source Servers
SMP application station does not support an automatic downgrade to SMP version 3.6. If downgrading, uninstall SMP before installing an older version. Before upgrading the application station, moving the application station to a different server, or preserving the SMP configurations for future installations, back up the following files: SMP installation folder\log SMP installation folder\bin\iLOIP.lst SMP installation folder\bin\hpvmm.conf...
Page 21: Installing Smp On The Application Station
Installing SMP on the application station To install SMP, you must have administrative rights. However, any user can access the application after SMP is installed. SMP must be installed on the application station to perform an SMP migration. Use the following procedure to install SMP on an application station or on an HP SIM server. Insert the SMP Boot CD in the CD drive of the selected application station.
Page 22 Click Next. The License Agreement screen appears. Read the license agreement, select I accept the agreement, and then click Next. Select the destination location for the SMP application. The default location is C:\Program Files\HP\HP Insight Server Migration software for ProLiant. Click Next.
Page 23 Enter the service credentials, and port changes if necessary, and then click Next. NOTE: To install SMP, you must have administrative rights. However, any user can access the application after SMP is installed. Click Finish. Installing SMP on the application station...
Page 24: Changing The Default Smp Application Station Service Port Number
Changing the default SMP application station service port number By default, SMP uses 51 124 as the default port for communications. Use one of the following methods to change the port: Change the port number during SMP installation. Manually change the port number after SMP installation. Edit the<SMP Installation Directory>\bin\hpvmm.conf file by adding the following line and saving the file: hpvmmsvcport=new SMP service port number on application station...
Page 25 Accessing the product documentation on the SMP Boot CD...
Page 27: Deploying Smp Agents
3 Deploying SMP Agents Deploying SMP Source Agents Before starting a migration, SMP 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 SMP 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.
Page 28: Smp Supported Windows Migrations
SMP supported Windows migrations Agent-less hypervisors HP integrated VMware ESXi 3.5 HP integrated VMware ESXi Update 1 HP integrated VMware ESXi Update 2 HP integrated VMware ESXi Update 3 HP integrated VMware ESXi Update 4 Citrix XenServer 5.0 HP integrated Citrix XenServer Microsoft Hyper-V™...
Page 29: Smp Boot Cds
The following are not supported with Linux migrations: Migrations with hypervisor Migrations installed with Windows in dual-boot mode Migrations to SAN disk Migrations with para-virtualized or non-standard kernels Migrations of LVM snapshots Migrations of Linux OS with encrypted partitions (Software RAID is not supported) Running any post-migration steps such as Linux Support Packs installation and HP SIM discovery SMP Boot CDs SMP Physical Boot CD—This is the default SMP CD.
Page 30: Deploying Smp Agent Through The Hp Sim Cms Quick Launch Feature
Deploying SMP Agent through the HP SIM CMS Quick Launch feature NOTE: If you are migrating a server with an older version of the SMP Application Station software installed, stop the SMP services before installing the SMP Source Agent. Select a source server to launch SMP Agent in HP SIM. Scroll over the Quick Launch feature, and then select Install SMP Agent.
Page 31: Deploying Smp Source Agent Directly From The Migration Wizard On The Application Station
Deploying SMP Source Agent directly from the Migration Wizard on the application station Open the SMP application, and then click the Migration Wizard tab. The Migration Wizard overview screen appears. Select the relevant OS type and the migration option, and then click Next. In step 1 of the Migration Wizard, enter the Server Name or IP address of the source server, and then select Deploy SMP Source Agent.
Page 32: Deploying Linux Smp Source Agent Locally On The Source Server
When SMP Source Agent is ready for migration, the following screen appears on the source machine. NOTE: The following screen appears only if X Windows was used. Record the IP addresses listed for the source server entry when using SMP. After the application station is connected to SMP Agent on these servers, the agent is locked to the application station.
Page 33 Copy the file in this folder to the source server, and then extract the file. To launch SMP Source Agent, go to the bin folder of the extracted directory, and then execute the script startHPSMPCnt.sh. When SMP Source Agent is ready for migration, the following screen appears on the source machine. Deploying SMP Source Agents...
Page 34: Installing Smp Source Agent On A Windows 2008 Server
NOTE: The following screen appears only if X Windows was used. Record the IP addresses listed for the source server entry when using SMP. After the application station is connected to SMP Agent on these servers, the agent is locked to the application station.
Page 35: Restarting The Smp Agent
Restarting the SMP Agent Table 3-2 Restarting SMP Agents on source and destination servers Agent type Windows SMP Source Agent On the agent console, click Abort and Exit, and then redeploy the agent. SMP VM Host Agent Restart the HP Server Migration Pack VM Host Agent service. SMP Agent running as part of Boot Restart the server and boot using the SMP Boot CD.
Page 36: Manually Creating And Booting A Virtual Machine Destination Server For P2V And V2V (Agent-Less)
found in the iLOIP.lst file. This file can be found at <install dir>\bin\. After all virtual media issues are resolved with the help of the command line interface, this file can be deleted.. The command line interface can be accessed from the bin folder of the install directory. At the command prompt, enter the following: ResetILOVM.cmd -i xxx.xxx.xxx.xxx -u username -p password Replace xxx.xxx.xxx.xxx with the iLO IP address.
Page 37: Automatically Creating And Booting A Virtual Destination Server Using The Smp Migration Wizard For P2V Or V2V
For Windows 2000 migrations, ensure that the storage controller selected is BusLogic. Ensure that the SMP Virtual Boot CD is attached to a Virtual CD-ROM device. HP integrated Citrix XenServer migration Ensure that the virtual machine has at least 600 MB of memory. Ensure that correct operating system for the virtual machine being created is selected.
Page 38 Review the system and storage configuration information to ensure the setup is correct. The system information section includes the following information: 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.
Page 39 (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.
Page 40 To launch the SMP Agent, click Next. When a message appears advising you that the destination server is ready for migration: Record the IP address listed on the screen for the destination server entry when using the SMP application. 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.
Page 41: Smp Overview Screen
If the SMP 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 SMP Agent no longer runs on the destination server. After the application station is connected to the SMP Agent on the destination server, the agent is locked to the application station.
Page 42 The SMP Overview screen has six tabs: Overview—This tab provides the following information or functions: Types of server migrations supported Migration steps overview Hyperlinks to access a PDF of the user guide and support matrix in a new window. 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.
Page 43: Licensing Smp
4 Licensing SMP This section provides information about SMP licensing. Licensing SMP One license key is required for each successful P2P, P2V, V2P, or V2V migration. SMP licenses, unlike other ProLiant Essentials licenses, do not need to be deployed to servers. SMP licenses are consumed after a successful migration.
Page 44: Adding Licenses
Subscription license Demo license Flexible Quantity license NOTE: For P2V or V2V, if several SMP or X2V Flexible Quantity license keys are installed, the licenses are processed in the following order: SMP license key X2V license key For P2P or V2P, if several P2P or X2P Flexible Quantity license keys are installed, the license keys are processed in the following order: P2P license key X2P license key...
Page 45: Migrating P2P Licenses Using License Migration Tool
Migrating P2P licenses using License Migration Tool If SMP is installed over an older P2P (SMP 2.x CMS) application, there is no need to use a migration tool when installing SMP. The SMP License Manager detects existing P2P licenses and imports them into the SMP during installation.
Page 46 The variable added appears in the System variables section. In the System variables section, double-click the path you just added. When the window appears, add a path for jre, bin, and jrewindows, and then click OK. To close the Systems Properties window, click OK. From the command window, enter the following: cd MigrateLM\bin migratex2xlic.cmd smp...
Page 47: Using Smp For Server Migration
5 Using SMP for server migration After source and destination server agents are launched, you can start a migration from an application station or HP SIM CMS by choosing one of the following: To start the Migration Wizard from a stand-alone application station, double-click the SMP icon on the desktop, or click Start Programs HP Insight Server Migration software for ProLiant HP Insight Server Migration software for ProLiant.
Page 48: Migration Wizard Page
The following conditions must be met to start a concurrent migration: The SMP Source Agent or Destination Boot CD should not be part of other running migrations. The Wizard blocks you from triggering multiple migrations from the same SMP Source Agent or to the same SMP Boot CD.
Page 49: Physical-To-Proliant (P2P) Migrations For Windows
Physical-to-ProLiant (P2P) migrations for Windows Preparing for a P2P migration The following sections list prerequisites for a Windows P2P migration. If you use a firewall, see the Configuring SMP with a firewall section in this guide. Source physical machine prerequisites A valid network connection must exist between the source and destination server.
Page 50: Performing A P2P Migration
Performing a P2P migration CAUTION: If the SMP application station shuts down or fails during any migration, then the migration being performed fails. Availability of application station during complete migration cycle is required for successful migration. To start the P2P Migration Wizard: If you are performing a migration from a stand-alone SMP application station: From the desktop, access the SMP Migration Wizard by clicking the SMP application icon.
Page 51 Click Next. To install SMP Source Agent on the source server, select the Deploy SMP Source Agent checkbox, enter the User name and Password, and then click Next. If SMP Source Agent is already running on the specified source server, make sure the Deploy SMP Source Agent checkbox is cleared, and then click Next.
Page 52 The Computed Destination Server Disk Requirement section lists the disks required on the destination server to support migrated volumes. The Size, Minimum Destination Size, and Maximum Destination Size values in the lower table are updated dynamically as volumes in the upper table are selected or cleared for migration.
Page 53 The Next and Previous buttons are disabled 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. The Next and Previous buttons are disabled during the reboot.
Page 54 10. Map source disks to destination disks. Ensure that migrated volumes fit on their mapped destination disks. Select the size of the migrated volumes on the destination server. The boot partition must be migrated to the first volume of the boot controller. If one active volume is migrated and the boot controller on the destination server can be identified, the boot partition is migrated to the first volume of the boot controller.
Page 55 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 to for the destination disk. Destination Size—This column displays the partition or disk resize on the destination disk. Migration Overhead—This row displays the additional space that must be reserved on the destination disk to accommodate disk geometry differences.
Page 56 When you click Begin Migration, the SMP Agent performs a final network check. If the network check fails, an error message appears. Fix the network issue, and then to continue the migration process, click Begin Migration again. 14. Review the migration progress details. To cancel the migration, click Cancel. After the entry in the Job Status field indicates the migration has been canceled, reboot the source and destination servers.
Page 57: P2P Post-Migration Tasks
P2P post-migration tasks After you complete a P2P migration, perform the following steps: Log in with administrative rights. At each of the Welcome to the Found New Hardware wizard screens, click Cancel. When prompted to reboot the system at the System Settings Change Window, click No. Install the latest PSP (if this option was not selected during the P2P install).
Page 58: Source Physical Machine Prerequisites
Source physical machine prerequisites A valid network connection must exist between the source and destination server. 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.
Page 59 If you are performing a migration from a stand-alone SMP application station: From the desktop, access the SMP Migration Wizard by clicking the SMP application icon. From the Overview page, click the Migration Wizard tab. Choose the Linux migration type. Click Physical to ProLiant Migration (P2P), and then click Next.
Page 60 NOTE: For Linux SMP Source Agent deployments, verify SELinux is in passive mode on the source server. If SMP Source Agent is already running on the specified source server, make sure the Deploy SMP Source Agent checkbox is cleared, and then click Next. The wizard verifies if SMP Source Agent is already running on the specified source server.
Page 61 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.
Page 62 indicating the number of logical units that must be created on the destination server. Additional space might be required to accommodate disk geometry differences. Manual - Boot destination server myself—If the destination server is booted to the SMP Boot CD and the destination agent is launched, select this option.
Page 63 10. Map source disks to destination disks. Ensure that migrated disks fit on their mapped destination disks. The boot partition must be migrated to the default boot disk of the boot controller. If one active volume is migrated and the boot controller on the destination server can be identified, the boot partition is migrated to the default boot disk of the boot controller.
Page 64 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 to for the destination disk. Destination Size—This column displays the partition or disk resize on the destination disk. Migration Overhead—This row displays the additional space that must be reserved on the destination disk to accommodate disk geometry differences.
Page 65 12. Click Next. 13. Review and confirm the migration details, and then click Begin Migration. Physical-to-ProLiant (P2P) migrations for Linux...
Page 66: P2P Post-Migration Tasks
When you click Begin Migration, the SMP Agent performs a final network check. If the network check fails, an error message appears. Fix the network issue, and then to continue the migration process, click Begin Migration again. 14. Review the migration progress details. To cancel the migration, click Cancel. After the entry in the Job Status field indicates the migration has been canceled, reboot the source and destination servers.
Page 67: Physical-To-Virtual (P2V) Migrations
entry to the boot.ini file. The original boot entry is preserved with a different name. The new boot entry contains functions to make disk checking more informative and to increase logging during the boot operation. These functions help you determine the success of the migration and can be disabled at any time after migration by modifying the boot.ini file.
Page 68: Destination Virtual Machine Host Or Virtual Machine Prerequisites
Disable all the Windows network drive mappings to the source physical machine in the SMP application station. Verify that the SMP application station Windows operating systems version is greater than or equal to the source physical machine Windows operating system version. Verify that the SMP application station Windows operating system is configured for NTFS.
Page 69 Choose the Windows migration type. Click Physical to Virtual Migration (P2V), and then click Next. If you are performing a migration from HP SIM CMS, choose one of the following options: To launch SMP using the HP SIM menu, select Deploy SMP Migration Tools Physical to Virtual (P2V), select Windows, and then follow the instructions to launch SMP Migration Tools.
Page 70 CD to the source server, and then install the SMP Source Agent by clicking Install SMP Source Agent in the auto run window of the SMP application. Select the volumes to be migrated. Volumes marked as active are selected by default. You cannot migrate or select unsupported file systems.
Page 71 The Computed Destination Server Disk Requirement section lists the disks required on the destination server to support migrated volumes. The Size, Minimum Destination Size, and Maximum Destination Size values in the lower table are updated dynamically as volumes in the upper table are selected or cleared for migration.
Page 72 NOTE: The VM Host agent must be deployed on the destination VM Host before completing this step. Agent-less hypervisors—Enter the destination virtual machine host name or IP address, and then enter the host administrative credentials. If the destination virtual machine was booted with the SMP Virtual Boot CD, select Manual Boot - Manually create VM through VM Host's Infrastructure Client.
Page 73 If the destination virtual machine is not created, select Auto Boot - Automatically have VM created through SMP migration. Enter the four-part VM Pre-boot IP address, Subnet Mask, and Gateway (optional) to be assigned to the virtual machine, and then click Next. Physical-to-virtual (P2V) migrations...
Page 74 Specify the destination disks, and then select the NTFS partitions to be resized. By default, this page includes a table that displays all disks present on the destination virtual machine, with source disk, disk format, size, and destination disk information. The following screen appears when the manually booted destination is selected for agent-less virtual machine hosts.
Page 75 Select the storage location (if applicable). If you are migrating to an agent-based virtual machine, to browse for guest storage location information, click Browse. A selection window appears where you can enter the destination folder information or select a remote folder. Click OK. If the destination virtual machine host is ESX 3.
Page 76 30 seconds 60 seconds If the source-to-destination or application-station-to-destination connection cannot be established, the Next button is disabled. Ensure that ports 51 125 and 51 126 are open between source and destination servers. If the source-to-destination or application-station-to-destination connection is established but the network test reports a transfer speed below 250 kbps, the Next button is disabled.
Page 77 1 1. Review and confirm the migration details, and then click Begin Migration. Physical-to-virtual (P2V) migrations...
Page 78 When you click Begin Migration, the SMP Agent performs a final network check. If the network check fails, an error message appears. Fix the network issue, and then to continue the migration process, click Begin Migration again. 12. Review the migration progress details. To cancel the migration, click Cancel. After the entry in the Job Status field indicates the migration has been canceled, reboot the source and destination servers.
Page 79: P2V Post-Migration Tasks
P2V post-migration tasks After you complete a P2V migration, perform one of the following based on your hypervisor type, and then perform the tasks in the seven steps that follow on the migrated virtual machine guest: Agent-less hypervisor—If you performed a migration to an agent-less hypervisor where you manually booted the virtual machine using the SMP VM Boot CD, you must disconnect the SMP VM Boot CD, and then manually reboot the virtual machine.
Page 80: Virtual-To-Virtual (V2V) Migrations
Modify the system host name. Perform one of the following: For VMware products, install the VMware Tools in the virtual machine. For Microsoft Virtual Server 2005, install Virtual Machine Additions in the virtual machine. For HP integrated Citrix XenServer, install Xen Guest Tools in the virtual machine. For Hyper-V, install Integration Tools in the virtual machine.
Page 81: Source Physical Machine Prerequisites
Source physical machine prerequisites CAUTION: If the SMP application station shuts down or fails during any migration, then the migration being performed fails. Availability of application station during complete migration cycle is required for successful migration. Because the SMP application does not migrate virtual machine guests with the following disk types, verify that these disk types do not exist on the source virtual machine.
Page 82: Destination Virtual Machine Host Or Virtual Machine Prerequisites
then download and install it from http://www.microsoft.com. Other versions of the initiator, including later versions, cannot be used with this version of SMP. Valid migrated previous P2P licenses or SMP X2P or X2X license keys are required on the application station.
Page 83 Choose the Windows migration type. Click Virtual to Virtual Migration (V2V), and then click Next. If you are performing a migration from HP SIM CMS, choose one of the following options: To launch SMP using the HP SIM menu, select Deploy SMP Migration Tools Virtual to Virtual (V2V), select Windows, and then follow the instructions to launch SMP Migration Tools.
Page 84 CD to the source server, and then install the SMP Source Agent by clicking Install SMP Source Agent in the auto run window of the SMP application. Select the volumes to be migrated. Volumes marked as active are selected by default. You cannot migrate or select unsupported file systems.
Page 85 The Computed Destination Server Disk Requirement section lists the disks required on the destination server to support migrated volumes. The Size, Minimum Destination Size, and Maximum Destination Size values in the lower table are updated dynamically as volumes in the upper table are selected or cleared for migration.
Page 86 If the destination virtual machine is not created, select Auto Boot - Automatically have VM created through SMP migration. Enter the four-part VM Pre-boot IP address, Subnet Mask, and Gateway (optional) to be assigned to the virtual machine, and then click Next. If the virtual machine host has an agent-based operating system, click Next.
Page 87 By default, this page includes a table that displays all disks present on the destination virtual machine, with source disk, disk format, size, and destination disk information. The following screen appears when the manually booted destination is selected for agent-less virtual machine hosts.
Page 88 The following screen appears when the automatically booted destination is selected for agent-less virtual machine hosts. If you are migrating to an agent-based virtual machine host or migrating to an agent-less virtual machine host that is automatically booted with the SMP Virtual Boot CD: Enter information in the Guest Display Name, Guest Memory, Guest Storage Location, and Virtual Switch boxes.
Page 89 If the destination virtual machine is booted with the SMP Virtual Boot CD, select the destination disk, and then click Next. 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 to which a partition or disk can be resized for the destination disk.
Page 90 10. Select the post-migration tasks, and then click Next. Select whether the SMP 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.
Page 91 1 1. Review and confirm the migration details, and then click Begin Migration. Virtual-to-virtual (V2V) migrations...
Page 92: V2V Post-Migration Tasks
When you click Begin Migration, the SMP Agent performs a final network check. If the network check fails, an error message appears. Fix the network issue, and then to continue the migration process, click Begin Migration again. 12. Review the migration progress details. To cancel the migration, click Cancel. After the entry in the Job Status field indicates the migration has been canceled, reboot the source and destination servers.
Page 93: Virtual-To-Proliant (V2P) Migrations
[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 SMP Preserved: Windows Server 2003, Enterprise /userva=3030 /3gb /noexecute=optout /fastdetect Virtual-to-ProLiant (V2P) migrations A virtual-to-ProLiant (V2P) migration enables migration of a virtual machine guest to a physical ProLiant server.
Page 94: Smp Application Station Prerequisites
Disable all applications and background services on the source machine. After the migrated machine has synchronized with the new hardware and is assigned a unique network identity, appropriate applications can be manually re-enabled and configured for the new environment. Temporarily disable HP Management Agents on the source physical machine. Verify that a Windows NT boot loader (NTLDR) is installed.
Page 95 Choose the Windows migration type. Click Virtual to ProLiant Migration (V2P), and then click Next. If you are performing a migration from HP SIM CMS, choose one of the following options: To launch SMP using the HP SIM menu, select Deploy SMP Migration Tools Virtual to ProLiant (V2P), select Windows, and then follow the instructions to launch SMP Migration Tools.
Page 96 CD to the source server, and then install the SMP Source Agent by clicking Install SMP Source Agent in the auto run window of the SMP application. Select the volumes to be migrated. Volumes marked as active are selected by default. You cannot migrate or select unsupported file systems.
Page 97 The Computed Destination Server Disk Requirement section lists the disks required on the destination server to support migrated volumes. The Size, Minimum Destination Size, and Maximum Destination Size values in the lower table are updated dynamically as volumes in the upper table are selected or cleared for migration.
Page 98 Auto Boot - Let SMP boot the destination server—If the destination server is not booted to the SMP Boot CD and the destination agent is not launched, select this option. The Next and Previous buttons are disabled during the reboot. To view the booting process of the destination server, click Launch iLO, and then open the remote console.
Page 99 1 1. Map source disks to destination disks. Ensure that migrated volumes fit on their mapped destination disks. Select the size of the migrated volumes on the destination server. The boot partition must be migrated to the first volume of the boot controller. If one active volume is migrated and the boot controller on the destination server can be identified, the boot partition is migrated to the first volume of the boot controller.
Page 100 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 to for the destination disk. Destination Size—This column displays the partition or disk resize on the destination disk. Migration Overhead—This row displays the additional space that must be reserved on the destination disk to accommodate disk geometry differences.
Page 101 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.
Page 102: V2P Post-Migration Tasks
When you click Begin Migration, the SMP Agent performs a final network check. If the network check fails, an error message appears. Fix the network issue, and then to continue the migration process, click Begin Migration again. 15. Review the migration progress details. To cancel the migration, click Cancel. After the entry in the Job Status field indicates the migration has been canceled, reboot the source and destination servers.
Page 103: San Migrations
Additionally, to retain the original boot parameters, copy all valid flags from the original entry and consider other appropriate boot flags as applicable, such as adding the /3GB flag only if the destination physical machine is configured with sufficient RAM. Then delete the original (preserved) entry, shown as struck through in the following example.
Page 104: Smp Application Integration To Hp Sim
A SAN migration of Windows 2000 Server or Advanced Server (with SP4) to a destination server with the Emulex LPe1 105-HP 4Gb FC HBA might cause a blue screen on the destination server. To resolve this issue: In step 6 of the Migration Wizard, do not select Perform post-migration steps after successful migration.
Page 105 An option also exists to have the HP SIM-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: Launch SMP from HP SIM. Select Deploy SMP Migration Tools Type of Migration, and then select a migration option.
Page 106: Launching Smp Migration Through Hp Sim
Click the Display servers Discovered in SIM checkbox. If HP SIM 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 HP SIM are filtered in the Show Host List to display the proper system type for each action.
Page 107 HP SIM verifies the source server or source virtual machine. If the selected server or virtual machine fails to satisfy the criteria to launch SMP migration, then the HP SIM task wizard appears, the Next button is disabled, and the migration cannot proceed. SMP application integration to HP SIM 107...
Page 108 If the selected server or virtual machine meets the criteria, then the SMP application opens in a new browser with the IP address of the selected host added in step 1 of the SMP application Migration Wizard. 108 Using SMP for server migration...
Page 109: Quick Launch Details
If a different host needs to be selected, then click Show Host List. All selected hosts discovered in HP SIM 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.
Page 110: Performing Post-Migration Steps For Windows 2000, Windows 2003, And Windows 2008
HP SIM verifies the source server or source virtual machine. If the selected server or virtual machine fails to satisfy the criteria to launch SMP migration, then the Quick Launch list does not display the unsupported migration options. If the selected server or virtual machine meets the criteria, then the SMP application opens in a new browser with the IP address of the selected host added in step 1 of the SMP application Migration Wizard.
Page 111 Click the Software tab, and then click Custom installation of the PSP for Windows 2000. PSP scans for available bundles to install. After the scan is complete, scroll down, and then click Install. Performing post-migration steps for Windows 2000, Windows 2003, and Windows 2008 1 1 1...
Page 112 To ensure that the drivers are installed properly after a P2P migration, select the Allow components to overwrite newer or up-to-date versions checkbox. To begin the installation, click Next. 1 12 Using SMP for server migration...
Page 113: Windows 2003 And Windows 2008 Post-Migration Steps
Windows 2003 and Windows 2008 post-migration steps To install PSP with Windows 2003 and Windows 2008: Insert the SmartStart CD in the local CD drive, or use virtual media. The HP SmartStart CD home page appears. Select the Software tab, and then click Custom installation of the PSP for Windows 2003 and Windows 2003x64.
Page 114 The HP SmartStart Update Manager begins. To install the PSP on the local host, select Local Host, and then click Next. 1 14 Using SMP for server migration...
Page 115 The HP SmartStart Update Manager automatically checks for installed items. After the search is completed, the Select Bundle Filter screen appears. Performing post-migration steps for Windows 2000, Windows 2003, and Windows 2008 1 15...
Page 116 To ensure that the drivers are installed properly after a P2P migration, in the Set Options for Bundle Filter section, select the FORCE ALL BUNDLE UPDATES checkbox. To continue, click OK. The Select items to be installed screen appears. To start the installation, click Install. 1 16 Using SMP for server migration...
Page 117: Viewing Migration Logs
6 Viewing migration logs Viewing migration logs The View Status/Logs tab has the following sections: View Currently Running Migration(s)—This section displays the status of the running jobs. It also has links to the source, target, and application station log files. If you need to cancel a migration in process, click Cancel.
Page 118 To view migration logs, scroll through the View Migration Result Log table. If there are enough logs of performed migrations, you must scroll through the migration logs table. The View Migration Result Log 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.
Page 119: Uploading Drivers
7 Uploading drivers The Upload Drivers tab displays the status of iSCSI initiator installed and all PSPs added to the application station for SMP. PSPs executables can be uploaded from this console when SMP is launched as a standalone product or when SMP is launched from HP SIM.
Page 121: Troubleshooting
8 Troubleshooting Troubleshooting Installation When launching the SMP wizard immediately after installation, the message Unable to communicate with the SMP service displays on the wizard page Usually, the service manager shows that SMP 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.
Page 122: Configuration
If you need to downgrade to an older version of the P2P application, you must use the following installation order: Uninstall the older version of P2P application. Install SMP. Configuration Ports required for SMP are not available This issue occurs if port numbers 51 124, 51 125, 51 126, or 51 127 have been locked by another application. To verify, choose one of the following: For Microsoft Windows Server™...
Page 123: Microsoft Dns Server Might Not Map The Host Name To Dhcp-Generated Ip Addresses
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). Microsoft DNS Server might not map the host name to DHCP-generated IP addresses If you use DHCP on the VMware ESX host, the Microsoft DNS server might not map the host name to DHCP-generated IP addresses.
Page 124: Source Server Identification Fails
The Windows 2000 Plug and Play (PnP) process might result in a system bug check if all of these conditions are met: The source server is running Windows 2000 Server or Windows 2000 Advanced Server. The source server has the HP iLO Management Channel Interface driver version 1.7.2195.0 or later installed.
Page 125: Smp Agent Deployment Fails
The destination server is unavailable or has ping (echo ICMP) disabled. The user credentials provided have administrative access. If the issue persists, manually deploy the agent. SMP Agent deployment fails SMP Agent might fail deployment because of the following: Incorrect user name or password—Verify that you have provided valid credentials with administrative rights for the source physical machine for the SMP Agent deployment.
Page 126: Smp Source Agent Installation Takes Longer Than Usual
SMP Source Agent installation takes longer than usual If the installation of the SMP Source Agent takes longer than usual, then refer to the SMP source server console or the SMP Source Agent log file for more information. You can find the SMP Source log files at C:\hpsmpagent.log on the source server.
Page 127: Mouse Does Not Work On A Virtual Machine Booted With The Smp Vm Boot Cd For Virtual Machines
Possible causes for the error message include: Network card is not connected to the network. Network to which the card connects to does not have DHCP. Network card is not supported by the SMP Boot CD. Make sure you are using a supported server using the HP Insight Server Migration software for ProLiant Support Matrix .
Page 128: Static Ip Address Cannot Be Assigned On The Destination Server While Booting Using The Boot Cd
Static IP address cannot be assigned on the destination server while booting using the Boot CD 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.
Page 129: Destination Server Boots From The Smp Boot Cd On A Manual Boot
Network on both the source and the SMP station must be properly working. The root login must be enabled on the destination ESX 3. x host, and root credentials are used for deploying agent to the host. To deploy the agent: Edit the /etc/ssh/sshd_config file.
Page 130: For Windows 2000
For Windows 2000 From the Control Panel, double-click System. In the System Properties window, click the Advanced tab. Click Performance Options. In the Virtual Memory section in the Performance Options window, click Change. In the Drive column, select the drive that contains the paging file to be changed. In the Paging file size for selected drive section, enter a new paging file size in the Initial size (MB) box.
Page 131: Smp Cannot Perform V2V Migrations On Virtual Machine Guests With Certain Disk Types
To resolve this issue: If an existing disk already containing some Windows partitions is used as the destination for migration, format the disk before using it as a destination disk. SMP cannot perform V2V migrations on virtual machine guests with certain disk types SMP does not move, copy, or migrate virtual machine guests with the following disk types.
Page 132: Error During Data Copy Of Linux Migration
To return to the original configuration, reboot the source server to Profile 1 Hardware Profile. Remove SMP Source Agent Mode manually. Right-click My Computer, and then select Properties. Click the Hardware tab, and then select Hardware profiles. Select SMP Source Agent Mode, and then click Delete. Before starting a new migration, verify that all antivirus and firewall software is properly reconfigured or disabled.
Page 133: Error Message Appears During P2P Installation
Access the Driver tab, and then click Update driver. Proceed through the steps and point to oemsetup.inf at the location where you have placed the downloaded Boot from SAN HBA driver. For all Emulex HBA devices seen in the Windows device manager, repeat step 4. After the driver update, restart the destination server.
Page 134: Destination Server Mouse And Keyboard Do Not Work
Destination server mouse and keyboard do not work The mouse and keyboard might not be operational immediately: On the destination server after a migration On a c-Class server blade after performing a Windows 2000 migration To detect and activate the mouse and keyboard, reboot the destination server so that PnP correctly detects and activates the mouse and keyboard.
Page 135: Virtual Machine Hosts Integrated Components Do Not Install On The Destination Virtual Machine Following Smp Migration
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. For more information, see http://support.microsoft.com/kb/269155/en-us. Virtual machine hosts Integrated Components do not install on the destination virtual machine following SMP migration To resolve this issue:...
Page 137: Hp Support And Contact Information
9 HP support and contact information HP Software Technical Support and Update Service HP offers a number of software support services, many of which are provided to our customers at no additional charge. Software Technical Support—HP Insight Server Migration software for ProLiant includes one year of 24 x 7 HP Software Technical Support Service.
Page 138: Support And Information
Support and information For HP support and software updates for SMP, see the following resources: http://www.hp.com/go/insight HP Insight Server Migration software for ProLiant User Guide HP Insight Server Migration software for ProLiant Release Notes For additional information about HP SIM, see the following resources: http://www.hp.com/go/hpsim HP SIM Technical Reference Guide HP Systems Insight Manager Help Guide...
Page 139: A Portable Images Network Tool (Pint)
A Portable Images Network Tool (PINT) The Portable Images Network Tool (PINT) automates NIC configuration on the destination servers during a migration. For more information on PINT, see the PINT readme files at system drive\Program Files\HP\HP Insight Server Migration software for ProLiant\PINT. PINT can only be use with specific servers.
Page 141: Glossary
Glossary HP SIM Central Management Server. guest operating A reference to a distinct operating system instance running in a virtual machine. system host operating A reference to the operating system that is the foundation for a virtual machine. system HP ProLiant A multiserver deployment tool that enables IT administrators to easily configure and deploy large Essentials Rapid volumes of servers in an unattended, automated fashion.
Page 143: Index
Index controllers appears as unknown, 128 CPU resources and memory on the application station, 15 accessing System page, 47 creating AdapterMismatch message appears, 133 virtual machine manually, 36 adding license keys, 44 critical or hardware-dependent application preparation, antivirus software, 17 application preparation, critical or hardware-dependent, application station Deploy Agent task fails, 124, 128...
Page 144 using with SMP, 18 FAQs, 121 firewalls, 16, 122 memory and CPU resources on the application station, 15 menus missing in SMP, 121 Microsoft DNS Server does not map the host name to hardware DHCP-generated IP addresses, 123 requirements, 19 Microsoft Small Business Server, 16 hardware support, 14 migration process...
Page 145 resizing volumes for Windows migration, 17 physical-to-virtual migrations, 67 virtual-to-ProLiant migration, 93 virtual-to-virtual migration, 80 OpenSSH requirements, 19 prerequisites operating system requirements, 28 physical-to-ProLiant source virtual machine host, 49, 57 operating system support, 14 physical-to-virtual source virtual machine host, 67 overview virtual-to-ProLiant source virtual machine, 81, 93 application station, 13...
Page 146 software requirements, 19 mouse stops working after migrating a Hyper-V virtual source preparation machine to a ProLiant server, 134 troubleshooting, 123 NTFS partitions cannot be resized from Windows 2008, source server identification fails, 124 NTFS resize error message, 130 migration fails to terminate, 130 P2P migration, 133 overview, 13 P2V migration, 133...
Page 147 creating using the SMP Migration Wizard, 37 creating using the SMP VM Boot CD, 36 manually booting, 36 manually creating, 36 mouse does not work, 127 virtual machine guest tools, 15 virtual machine hosts prerequisites for P2P migration destination, 49, 58, 94 prerequisites for P2V migration destination, 68, 82 requirements, 20 virtual-to-ProLiant...

This manual is also suitable for:

234664-002 - proliant - ml330t02 Bl10e - hp proliant - 512 mb ram Dl590 - hp proliant - 1 gb ram Dl180 - g6 e5504 2x2gb 4lff svr Dl360 - proliant - photon Ml350 - proliant - g2 ... Show all

Compaq 226824-001 - ProLiant - ML750 User Manual

About this Document

1 Introduction

2 SMP Installation and Configuration Requirements

3 Deploying SMP Agents

4 Licensing SMP

5 Using SMP for Server Migration

6 Viewing Migration Logs

7 Uploading Drivers

8 Troubleshooting

9 HP Support and Contact Information

A Portable Images Network Tool (PINT)

Glossary

Index

Quick Links

User Guide

Related Manuals for Compaq 226824-001 - ProLiant - ML750

Summary of Contents for Compaq 226824-001 - ProLiant - ML750

This manual is also suitable for:

Table of Contents