Hp Insight Control Manuel d'utilisateur

HP Insight Control 6.3 Server MigrationUser GuideAbstractHP Insight Control server migration provides an automated, accurate and affordable way to mig

1 Server migration introductionOverviewHP Insight Control server migration provides an automated, accurate and affordable way to migrateexisting serve

Table 1 Related productsDescriptionProductUsed to solve networking issues (specifically, NICconfiguration issues) when moving operating system imagesb

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 page has the following tabs:•

• Upload DriversThis tab displays the status of the iSCSI Initiator installed on the server and provides the optionto upload PSP executable files. Thi

Part II Pre-migration tasksThis part of the guide assists you in collecting information to prepare for a migration, and covers steps 1and 2 of the “Mi

3 Preparing hardware for migrationVerifying hardware and operating system supportBefore starting an X2P (P2P or V2P) migration, verify the following:•

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

• Volumes with bad clusters. The migration of volumes with bad clusters is not supported byserver migration and requires that you manually migrate vol

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

© Copyright 2011 Hewlett-Packard Development Company, L.P.Confidential computer software. Valid license from HP required for possession, use or copyin

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

Part III MigrationThis part of the guide contains information related to steps 3 through 5 of the“Migration checklist” (page 12),and methods for manua

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, you must install theX.Org X11 libXtst runtime library libXtst-1.0.99.2-3.el6.

Manually running server migration Source Agents on source serversDeploying a Windows server migration Source Agent locally on the source server1. Acce

Figure 5 Windows Source Agent screen4. Record the IP addresses listed for the source server entry when using Insight Control servermigration.After the

Deploying the Linux server migration Source Agent locally on the source server1. Access the server migration Source Agent in the following folder on t

NOTE: The server migration Source Agent uses a 32–bit Java Runtime Environment. In 64–bitRHEL, the Linux source migration agent window does not appear

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 Destination Size, chosen when specifyingdestination disks in the migration wizard, does no

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

2. In step 3 of the P2P or V2P migration wizard, select Auto Boot - Let server migration boot thedestination server.3. Enter the iLO IP address and iL

Prerequisites for VMware ESX migrationEnsure that the following parameters are met:• The virtual machine has at least 600 MB of memory.• Create the vi

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

see http://www.microsoft.com/kb/311272 (or search for “DevCon” on the microsoft.comwebsite.) Do not extract the binary that you download from the Micr

• The primary storage controller is configured with drives attached.• The destination server is booted to the Insight Control server migration Boot CD

• The GRUB Boot Loader is the primary boot loader on the source server.• Guest tools are uninstalled.Destination physical server prerequisitesIf migra

NOTE: To migrate Windows 2003 to a SAN-connected destination server, you must first installService Pack 2, and the updated Storport storage driver (se

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

Figure 9 Identify the source server4. Click Show Host to view the server IP address, name, and OS details. If you manually deployedthe source Agent, c

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

Uninstalling guest tools...23Choosing server migra

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

9 Post-migration tasksInstalling ProLiant Support Packs after migrationIf you performed a Windows X2P migration, and you did not upload the Windows PS

After the virtual machine reboots, you must perform the following steps on the destination virtualmachine guest for hypervisors.1. Modify the system h

b. If the IP addresses are static, reassign them.5. If the license is not a volume license, then reactivate it.6. The mouse and keyboard might not be

3. Compare random samples of files and directories between the source and the destinationservers to ensure that the data has been migrated successfull

Part IV Troubleshooting and support

10 TroubleshootingRegister to receive customer advisories via email. See the Insight Software Installation and UpgradeRelease Notes at the following w

Launching server migration from Systems Insight Manager throws an exceptionWhen launching server migration through Systems Insight Manager, an excepti

3. Verify that the source server can be reached from the application station. Communication onnetwork ports 51125 and 51126 must be enabled by any fir

• A "Client for Microsoft Networks" client must be present in the network interface propertieson the source server and the CMS.Linux Source

X2P post-migration tasks (Linux)...42X2V post-migration tasks

• Turn off the hypervisor using the following command:bcdedit /set hypervisorlaunchtype offAfter the migration, you can re-enable the hypervisor using

Mouse does not work on a virtual machine booted with the Insight Control servermigration Virtual Machine Boot CD ISOCauseThis issue occurs because vir

The destination server displays a blank screen when booting to server migration BootCD ISOThe destination server might display a blank screen when boo

3. Open Advanced Options, and then select Restore Settings/Erase Boot Disk or Clear NVRAM.4. Reboot the system using the Insight Control server migrat

Application station fails to connect to the destination server when the server isauto-booted for an X2P migrationThe application station can fail to c

Migrating a Linux source server with very large storage fails when the migration isinitiatedMigrating Linux source servers with very large storage may

Suggest actionProceed with the migration.Migration hangs if source server is shut downIn some network, firewall, or router configuration scenarios, In

The File System on Source Disk \\.\PhysicalDrive0, Partition 0 Could Not Be ResizedDuring the MigrationMigration might fails with the error The file s

Suggested actionTo start a new migration:1. Restart the migration agent on the source and destination servers.2. On the application station, close the

SAN-connected destination server displays blue screenSuggested actionTo migrate Windows Server 2003 to a SAN-connected destination server, install the

Suggested action...50Mouse does not work on a virtu

Windows server migration Source Agent or PINT remote deployment is intermittentand deployment fails with General failure occurred errorWhen you remote

Destination server mouse and keyboard do not work after a Windows migrationThe mouse and keyboard might not be operational immediately on a destinatio

◦ Verify if the server has the following files:Hidusb.sys–– Hidkbd.sys– Mouhid.sysReinstall the mouse and keyboard drivers with one of the following m

Suggested actionDepending on the operating system, perform the following task:1. Open Windows Disk Management.2. Correct the incorrect letter assignme

2. Add a CD-ROM drive to the virtual machine.3. Power up the virtual machine, and then restart the installation of the Integrated Components.Exclamati

Suggested ActionFollow the suggestion provided in the warning message to resolve the issue.Once the issue is resolved, any disk can be added (which ma

11 Support and other resourcesContacting HPInformation to collect before contacting HPBe sure to have the following information available before you c

• HP Insight ControlDocumentation for Insight Control, including documentation for Insight Control virtual machinemanagement and Insight Control power

Book title The title of a book. On the web, this can be a hyperlink to thebook itself.Command A command name or command phrase, for example ls -a.Comp

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

ReiserFS volumes are blocked for Linux migration...56Cause...

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

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.72 Performing migrations in a Micro

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

IndexAantivirus software, 20application stationdescription, 12fails to connect to the destination server for X2P, 54auto booting destination server fa

Insight Control does not detect virtual machines on mappednetwork drives, 53Insight Control server migration serviceunable to communicate , 46installa

Linux , 42Linux P2V, 43validating the migration, 43Windows P2P, 41Windows P2V, 41pre-migration tasksinstalling ProLiant Support Packs for Windows, 20p

VV2P, 10source server prerequisites, 32V2V, 10booting a virtual destination server, 31source server prerequisites, 32using the migration wizard, 31val

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

Part I Overview and conceptsThis part focuses on conceptual information needed to understand the product. It does not include informationon how to use