Hp Insight Foundation Software for ProLiant Manuel d'utilisateur Page 1

HP Insight Control Server Migration 7.3Update 1 User GuideAbstractHP Insight Control server migration provides an automated, accurate, and affordable

Part I Overview and conceptsThis part focuses on conceptual information that will help to understand the product. It does not includeinformation on ho

1 Server migration introductionOverviewHP Insight Control server migration provides an automated, accurate, and affordable way tomigrate existing serv

Table 1 Related products (continued)DescriptionProductsettings, so that each computing device is maintained inthe right configuration.Facilitates the

2 Server migration conceptsServer migration componentsThe Insight Control server migration environment consists of the following required components:•

HP Insight Control server migration software tabsFigure 1 Migration screenThe Insight Control server migration software screen has the following tabs:

• Upload DriversThis tab displays the status of iSCSI Initiator and DISM installed on the server and providesthe option to upload HP ProLiant Support

Part II Premigration tasksThis part of the guide assists you in collecting information to prepare for a migration, and covers steps 1and 2 of the chec

3 Preparing hardware for migrationVerifying hardware and operating system supportBefore you start any X2P (P2P or V2P) migration, verify the following

4 Planning the migrationPlanning a migration strategyOne challenge in migrating operating systems, applications, and data is modifying the migratedope

might be recognized as RAW (partitions in which no file systems exist). Although servermigration can perform migrations on these volumes, it cannot re

© Copyright 2007, 2014 Hewlett-Packard Development Company, L.P.Legal NoticesConfidential computer software. Valid license from HP required for posses

5 Preparing software for migrationVerifying licenses for software to be migratedBefore you perform a migration, review all hardware, operating system,

Figure 2 TCP ports in use during migrationNOTE: Insight Control uses the following encryption types:• SSL RSA with RC4 128 MD5• SSL RSA with RC4 128 S

Installing Service Pack for ProLiantSPP contains sets of drivers and firmwares for the latest ProLiant Gen8 destination servers to get itupdated after

Part III MigrationThis part of the guide contains information related to steps 3 through 5 of the checklist provided in “Migrationchecklist” (page 13)

6 Preparing the source server and deploying the SourceAgentVerifying Windows source server requirementsThe physical or virtual Windows source server r

• To enable the display of the Linux source server agent in 64–bit RHEL, installation of the X.OrgX11 libXtst runtime library libXtst-1.0.99.2-3.el6.i

NOTE: Shut down any running hypervisor or virtual machines on the source server before youdeploy the migration Agent. Failure to do so can result in i

Figure 4 Server migration agent install screenWhen the server migration Source Agent is ready for migration, the following screen appearson the source

4. Record the IP addresses listed for the source server entry when using Insight Control servermigration.After the application station is connected to

Figure 7 Linux Source Agent screenNOTE: The server migration Source Agent uses a 32–bit Java Runtime Environment. In 64–bitRHEL, the Linux source migr

ContentsI Overview and concepts...101 Server migration introduction...

7 Preparing the destination server and deploying thedestination agentPrerequisitesPhysical destination serversA supported ProLiant destination server

Linux server migration can fail with the following error if the destination size chosen when youspecify destination disks in the migration wizard, doe

Booting a physical destination server automatically by using the migration wizard1. Identify the source server and select volumes to migrate in steps

• The boot virtual disk is connected to the 0th channel of the first IDE controller.• The Insight Control server migration Virtual Machine Boot CD ISO

NOTE: If the application cannot connect to the destination virtual machine, return to step 3 ofthe migration wizard. Then while leaving the migration

8 Migrating the serversPrerequisitesCAUTION: If the Insight Control application station shuts down or fails during any migration, themigration fails.

• SPP (Windows only)You can upload one or more SPPs when you select additional migration options from theserver migration wizard. When a SPP is select

• Comply with all minimum prerequisites as listed in “Minimum source server prerequisites forall migrations” (page 35).• During migration, the migrati

• Verify compliance with all minimum prerequisites. For more information, see “Minimum sourceserver prerequisites for all migrations” (page 35).• Make

Destination virtual machine host or virtual machine prerequisitesIf you are migrating to a destination virtual machine, verify that the following prer

7 Preparing the destination server and deploying the destination agent...30Prerequisites...

to a SAN LUN connected to a Fibre Channel HBA in the destination server, the server migrationmight not migrate to the primary LUN. Failing to disable

Figure 9 Identify the source server4. Click Show Server to view the server IP address, name, and OS details. If you manuallydeployed the Source Agent,

Figure 10 Quick Launch• From the All Systems page in the Systems Insight Manager console, select a source server,and then scroll over Quick Launch. Qu

3. Systems Insight Manager verifies the source physical server or source virtual machine.• If the selected server or virtual machine fails to satisfy

9 Postmigration tasksInstalling ProLiant Support Packs after migrationIf you perform a Windows X2P migration, without uploading the Windows PSP execut

X2V postmigration tasks (Windows)After you complete a X2V migration, perform the following steps on the destination server:1. If you manually booted t

3. Delete the original (preserved) entry.Example 1 Editing Boot.ini[boot loader]default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWStimeout=30[operatin

Viewing migration logsFrom the View Status/Logs tab, you can:• View currently running migrations.• View a log of the migration results.• Create suppor

Part IV Troubleshooting and support

10 TroubleshootingYou can register to receive customer advisories via email. For more information, see HP InsightManagement Installation and Upgrade R

Browser displays an error after loading the server migration wizard from Systems InsightManager...

Network Configuration page. The name is displayed as Broadcom Corporation, Unknowndevice instead of HP Ethernet 1Gb 4-port 331i-SPI Adapter.Suggested

1. Download and install WAIK version 3.0 for Windows 7 from the Microsoft Download Center.2. To make DISM tool available for the application server, p

1. Cancel execution of the migration agent.2. In the command prompt window, change to the root directory of the Windows disk.3. Run the following comm

• Make sure the source server and CMS are both either inside the same VPN or outside theVPN.• Make sure that 32-bit glibc is installed on 64-bit Linux

Migrating a source server fails with the Microsoft Hyper-V role enabledIf you are trying to migrate a source server with the Microsoft Hyper-V role en

Suggested actionTry the following:1. Power down the virtual machine.2. Ensure that the virtual machine has at least 1024 MB of RAM.3. Reboot to the In

3. If the Insight Control server migration Boot CD ISO cannot detect the storage controller, youmight need to reconfigure the storage controller envir

Suggested actionAssign a different IP address to the network adaptor or reboot the server.Supported storage controllers display Unknown on the Boot CD

Insight Control server migration stops responding during automatic booting ofMicrosoft Hyper-V virtual machineInsight Control server migration might s

Suggested actionBefore you migrate, you must disable the AMD virtualization or Intel Hyper-Threading in the BIOSof the destination server.Migration pr

Suggested action...55Destination server displays a

Linux migration might fail when X Windows configuration is not properly formattedLinux migrations might fail when the X Windows configuration file xor

volume or performing a "chkdsk /f" prior to the migration may resolvethis condition.CauseThis message appears when Insight Control server mi

Migration fails during the disk cloning phaseThe following message might appear on the application station log (hpsmpsvc.log) if thedestination server

Source Agent fails to launch when source server reboots in migration agent modeSuggested actionTry the following:1. To return to the original configur

Suggested actionAfter the P2P migration is complete, manually configure the IP address on the destination server.For specific instructions on performi

Migration of Windows 2008 or Windows 2012 from Physical Server—> PhysicalServer—> Physical Server, results in blue screen error.When Windows 200

scenarios include a tampered source, a Microsoft Hyper-V VM source, or a migrated source thatused PS/2 drivers.Suggested actionTry the following:• Reb

6. Install the latest PSP on the destination server.7. Remove the (dongle-attached) USB mouse devices and keyboards from the source anddestination ser

Mouse and keyboard do not work after a Microsoft Hyper-V virtual machine ismigrated to a ProLiant serverSuggested actionIf the mouse and keyboard do n

Network adapter in the destination ESX virtual machine is not initialized after a V2VmigrationThe network adapter in the destination ESX virtual machi

Suggested action...61Migration fails during the dis

to eject the boot CD and as a result, after the reboot, the VM will boot back into the boot CD. Thisissue is specific to Microsoft Hyper-V VMs.Suggest

2. Click Advanced and navigate to Security section under Settings.3. Clear the Do not save encrypted pages on disk check box.4. Click OK.This will ena

toroot (hd0,0)kernel /vmlinuz-2.6.32-269.el6.x86_64 ro root/dev/mapper/volGroup-lv_rotintel_iommu=on rd_NO_LUKS LANG-en_US.UTF-8 rd_NO_MDrd_LVM_LV=Vol

11 Support and other resourcesInformation to collect before contacting HPBe sure to have the following information available before you contact HP:• S

The service also provides access to software updates and reference manuals in electronic form asthey are made available from HP.With this service, Ins

3. Select the Download drivers and software (and firmware) option.4. Enter your server model (for example, BL460c G5) in the For product text box, and

... Indicates that the preceding element can be repeated one or moretimes.WARNING An alert that calls attention to important information that, if notu

12 Documentation feedbackHP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any errors, sugge

A Applying old server migration standalone licensesStarting with Insight Control 6.0, HP Insight Control server migration is no longer available as as

B Performing migrations in a Microsoft Cluster serverenvironmentMigrations in a Microsoft Cluster server environment often require you to move an oper

Mouse and keyboard do not work after a Microsoft Hyper-V virtual machine is migrated to aProLiant server...

2. Review the event logs and cluster logs to verify that there are no critical issues that might affectthe migration. If an Exchange or SQL Server is

15. Review the event logs and cluster logs to see if there are any issues occurring with the newlymigrated cluster.Post migration considerations and s

C Logging server migration application service Logs intoWindows NT EventsTo log the server migration application service logs into Windows NT Events,

GlossaryESX VMware ESX, a virtualization product produced by VMware, Inc.EVA Enterprise Virtual ArrayMSA Modular Smart ArrayTCP Transmission Control P

IndexAantivirus software, 21application stationdescription, 13fails to connect to the destination server for X2P, 58auto booting destination server fa

keyboarddoes not work when booting to the Insight Control CDISO, 55troubleshooting, 65, 68Llaunchingmigration wizard, 40migrations through Quick Launc

premigration tasksinstalling ProLiant Support Packs for Windows, 21Installing Service Pack for ProLiant, 22preparingapplication station requirements,

using the migration wizard, 33validating the migration, 47verifying licenses, 20virtual machinekernel panic when booting, 54mouse does not work, 55Vir

Suggested Action..........................7211 Support and other resou