HP Virtual Connect Enterprise Manager Software manual Booting the destination server

Page 29

Linux server migration can fail with the following error if Destination Size, chosen when specifying destination disks in the migration wizard, does not have enough space to create the <initrd name>-smpuefiles:

Server migration could not modify initrd on the destination server. This could happen when there is not enough free space available on boot partition. Increase free space on boot partition by deleting unused files or make sure that boot partition has 10MB or more of free space and retry migration process.

To resolve this issue, choose a Destination Size, when specifying destination disks in the migration wizard, that is large enough to create the /boot/<initrd name>-smpuefiles on the corresponding disk partition on the destination server.

Booting the destination server

Boot the destination server using the applicable Insight Control server migration Boot CD ISO. To boot a destination physical server, you must be able to reboot the server and load through iLO. For virtual machines, you must have access to the virtual machine host management console. For information on choosing server migration agents, see “Choosing server migration Agents” (page 23).

There are Boot CD ISO files available to boot destination servers manually. However HP recommends that you allow the server migration wizard to boot the destination server. You can do this by selecting the Auto Boot - Let server migration Boot the destination server option in Step 3 of the wizard. See “Booting a physical destination server automatically using the migration wizard” (page 30) or check the Insight Control server migration online help for more information.

•Insight Control server migration ProLiant Boot CD ISO file™

You can use this ISO to manually boot a physical destination server for X2P migrations. This ISO is available after you install Insight Control server migration. To access the ISO, see the directory <server migration installation directory>\Agents\SMP\smpbootcd-p-[version #].iso.

•Insight Control server migration Virtual Machine Boot CD ISO file™

You can use this ISO to manually boot the destination virtual machine guest for X2V migrations. This ISO is available after you install Insight Control server migration. To access the ISO, see the directory <server migration installation directory>\Agents\SMP\smpbootcd-v-[version #].iso.

The Insight Control server migration ProLiant or Virtual Machine Boot CD ISO can only boot supported destination servers. For a list of supported servers, see the HP Insight Management Support Matrix the following website:

http://www.hp.com/go/insightmanagement/docs

To manually or automatically boot the destination server or virtual machine to the proper Insight Control server migration Boot CD ISO, see the following procedures. After the destination system is booted, you must configure it to launch the destination agent.

Booting a physical destination server manually using the Insight Control server migration ProLiant Boot CD ISO for X2P migrations

NOTE: For Gen8 servers, manual boot option is not supported.

1.Boot the server remotely using the iLO virtual media feature.

2.After the destination server or virtual machine is booted to the proper Boot CD ISO file, use the Boot CD ISO application to configure the destination server and launch the destination Agent. From the Boot CD ISO application, click Help for instructions.

Booting the destination server

29

Page 28 Page 30
Image 29
Page 28 Page 30
Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents Post-migration tasks IV Troubleshooting and supportMigrating the servers ISO Contents Contents Glossary Index Support and other resourcesApplying old server migration standalone licenses Part I Overview and concepts Server migration introduction Installing and configuring server migration softwareOverview Related productsProduct Description Server migration concepts Migration checklistServer migration components Overview of migrating a serverMigration screen HP Insight Control server migration software tabsServer migration concepts Part II Pre-migration tasks Verifying application station system requirements Preparing hardware for migrationVerifying hardware and operating system support Planning the migration Resizing Linux file systems Verifying licenses for software to be migrated Preparing software for migrationMigration Security Disabling firewallsGenerating static or dynamic certificates Installing ProLiant Support PacksDisabling antivirus software Part III Migration Verifying Windows source server requirements Preparing the source server and deploying the Source AgentVerifying Linux source server requirements Preparing a Microsoft Hyper-V source serverChoosing server migration Agents Uninstalling guest toolsDeploying server migration Agents Deploying AgentsNavigate to server migration Source Agent Server migration agent install dialog Navigate to server migration Source Agent Linux Source Agent screen Linux destination size requirement PrerequisitesPhysical destination servers Virtual machine hostsBooting the destination server ILO boot prerequisites Manually creating and booting a virtual destination serverPrerequisites for VMware ESX migration Page Minimum source server prerequisites for all migrations Migrating the serversIf you use a firewall, see Disabling firewalls Preparing for a Windows server migrationPreparing for a Linux server migration SAN migrations in Windows Starting the migration wizard Launching server migrations using the Deploy menuVerify Source Physical server Quick Launch Launching server migrations using Quick LaunchAvailable operations Post-migration tasks Installing ProLiant Support Packs after migrationX2P post-migration tasks Windows X2V post-migration tasks WindowsX2P post-migration tasks Linux Edit the boot.ini file to activate a graphical boot processViewing migration logs X2V post-migration tasks LinuxValidating the migration Validating Linux migrationsPost-migration tasks Part IV Troubleshooting and support User interface TroubleshootingSource preparation Server migration wizard hangsMigration Agent deployment fails Source server identification failsSuggestion action Linux Source Agent window does not appear on Rhel 64-bitDestination server identification fails Destination preparationIncorrect LUN size detected in of the migration wizard Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Migration process Drivers cannot be installed or injected onto boot diskLarge volumes fail with server thread error Java.lang.OutOfMemoryError Java heap space Migration hangs if source server is shut down Ntfs resize error messageReiserFS volumes are blocked for Linux migration Migration fails during the disk cloning phase Error during data copy of Linux migration SAN-connected destination server displays blue screen Destination server boots with an invalid IP addressPerform one of the following Post-migrationHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Server is unresponsive during PSP installation Destination virtual machine fail to boot after X2V migrationReboot the server and then reinstall PSP manually Information to collect before contacting HP How to contact HPSupport and other resources Related information HP authorized resellersDocumentation feedback Related documentation Typographic conventionsTIP Applying old server migration standalone licenses Basic hardware design of a three-node duster Pre-migration consideration steps for clustersPost migration considerations and steps Performing the migrationPost migration considerations and steps Glossary Index Index SIM Websites
Top Page Image Contents