사용자 설명서차례HP Insight Control Server Migration 7.2 User Guide1Part I Overview and concepts101 Server migration introduction11Overview11Installing and configuring server migration software11Installing or upgrading server migration software11Licensing server migration11Related products112 Server migration concepts13Server migration components13Overview of migrating a server13Migration checklist13HP Insight Control server migration software tabs14Part II Premigration tasks163 Preparing hardware for migration17Verifying hardware and operating system support17Verifying system requirements for the application station174 Planning the migration18Planning a migration strategy18Preparing a schedule18Considerations for multiboot systems18Migrating large NTFS partitions18Resizing file systems for migration18Resizing Windows file systems18Resizing Linux file systems19Manually disabling critical or hardware-dependent applications195 Preparing software for migration20Verifying licenses for software to be migrated20Migration security20Disabling firewalls20Disabling antivirus software21Generating static or dynamic certificates21Installing ProLiant Support Packs21Installing Service Pack for ProLiant21Part III Migration236 Preparing the source server and deploying the Source Agent24Verifying Windows source server requirements24Preparing a Microsoft Hyper-V source server24Verifying Linux source server requirements24Removing guest tools25Choosing server migration Agents25Deploying server migration Agents25Deploying Agents25Manually running server migration Source Agents on the source server26Deploying a Windows server migration Source Agent locally on the source server26Deploying a server migration Source Agent on domain controllers28Deploying the Linux server migration Source Agent locally on the source server28Detecting, stopping, or restarting a remotely deployed server migration Source Agent297 Preparing the destination server and deploying the destination agent30Prerequisites30Physical destination servers30Virtual machine hosts30Linux destination size requirement30Booting the destination server31Booting a physical destination server manually by using the Insight Control server migration ProLiant Boot CD ISO for X2P migrations31Booting a physical destination server automatically by using the migration wizard32iLO boot prerequisites32Manually creating and booting a virtual destination server32Prerequisites for manually creating and booting a destination virtual machine32Prerequisites for booting a virtual machine in Microsoft Hyper-V32Prerequisites for VMware ESX migration33Manually creating and booting a virtual machine destination server for X2V33Automatically creating and booting a virtual destination server338 Migrating the servers35Prerequisites35Minimum source server prerequisites for all migrations35Uploading drivers35Preparing for a Windows server migration36Windows source server prerequisites36Source physical server prerequisites36Source virtual machine prerequisites37Destination physical server prerequisites37Destination virtual machine host or virtual machine prerequisites37Preparing for a Linux server migration37Source physical server prerequisites38Source virtual machine prerequisites38Destination physical server prerequisites38Destination virtual machine host or virtual machine prerequisites39SAN migrations in Windows39Starting the migration wizard40Launching server migration by using the Deploy menu40Launching server migration by using Quick Launch419 Postmigration tasks44Installing ProLiant Support Packs after migration44Installing Service Pack for ProLiant after migration44X2P postmigration tasks (Windows)44X2V postmigration tasks (Windows)45Editing the Windows boot.ini file after migration (Windows Server 2003)45X2P postmigration tasks (Linux)46X2V postmigration tasks (Linux)46Viewing migration logs47Validating the migration47Validating Linux migrations47Validating Windows migrations47Part IV Troubleshooting and support4810 Troubleshooting49User interface49Server migration wizard hangs49Cause49Suggested action49Browser displays an error after loading the server migration wizard from Systems Insight Manager49Cause49Suggested action49Launching server migration from Systems Insight Manager throws an exception49Cause49Suggested action49The name of HP Ethernet 1Gb 4-port 331i-SPI Adapter is not displayed correctly49Suggested action50Unable to launch server migration tools from Systems Insight Manager50Suggested Action50Static IP configuration fails on Hyper-V VM when configured using Boot CD50Cause50Suggested action:50Unable to migrate Windows 2008/2008 R2/2012 using Windows 2008 x64 CMS50Cause50Suggested Action50Source preparation51Corrective action is required before this server can be migrated51Cause51Suggested action51Source server identification fails51Suggested action51Migration Agent deployment fails52Suggested action52Linux Source Agent window does not appear on RHEL 64–bit52Suggested action53Remote deployment of Linux Source Agent using nonroot credentials fails53Suggested action53Manual installation of Linux Source Agent using sudo user privileges fails53Suggested action53Incorrect LUN size is detected in step 2 of the migration wizard53Cause53Suggested action53Migrating a source server fails with the Microsoft Hyper-V role enabled53Suggested action53Unable to boot Windows due to unsigned or corrupt drivers54Suggested action54Destination preparation54Destination server identification fails54Suggested action54IP address configuration fails on a manually booted virtual machine in Microsoft Hyper-V for a P2V or V2V migration54Suggested action54Kernel panic occurs in booting a virtual machine to the Insight Control server migration Virtual Machine Boot CD ISO54Suggested action55Mouse does not work on a virtual machine booted with the Insight Control server migration Virtual Machine Boot CD ISO55Cause55Suggested action55Primary array controller does not have logical drives defined55Suggested action55Primary controller configured in the system does not have drives attached55Suggested action55Primary controller in the system is not supported by this version of Insight Control server migration55Suggested action55Destination server displays a blank screen when it boots to server migration Boot CD ISO56Suggested action56Some storage volumes on the destination server are not available for selection56Suggested action56Static IP address cannot be assigned on the destination server while booting using the Boot CD ISO56Cause56Suggested action57Supported storage controllers display Unknown on the Boot CD ISO57Cause57Suggested action57Automatic booting of the destination physical server fails57Suggested action573 Insight Control server migration might not detect virtual machines on mapped network drives57Cause57Suggested action57Destination server does not boot even though the automatic booting option was chosen during X2P migrations57Suggested action57Insight Control server migration stops responding during automatic booting of Microsoft Hyper-V virtual machine58Suggested action58Application station fails to connect to the destination server when the server is automatically booted for an X2P migration58Cause58Suggested action58Warning message is not displayed for an unsupported server when the server is started using the Insight Control server migration ProLiant Boot CD58Suggested action58Microsoft Windows 2008 OS migration results in a blue screen error on destination server configured with NC551m FCoE card58Suggested action59Migration process59Drivers cannot be installed or injected onto a boot disk59Suggested action59Large volumes fail with a server thread error59Suggested action59Migrating a Linux source server that has large storage fails when the migration is initiated59Suggested action59Linux migration might fail when X Windows configuration is not properly formatted60Suggested action60Partitions created with third-party partitioning tools do not show the proper file system type in the server migration wizard60Suggested action60Migration hangs if the source server is shut down60Suggested action60NTFS resize error message appears61Cause61Suggested action61ReiserFS volumes are blocked for Linux migration61Cause61Suggested action61Filesystem on source disk \\.\PhysicalDrive0, Partition 0 could not be resized during the migration61Cause61Suggested action62Migration fails during the disk cloning phase62Cause62Suggested action62Failed: Drivers could Not Be Injected Into Boot Disk in the logs62Suggested action62Starting a new migration after a current migration is stopped62Suggested action62Unrecoverable sector-read errors on the source server hard drive are not supported and fail a Windows P2P or P2V migration62Cause63Suggested action63Source Agent fails to launch when source server reboots in migration agent mode63Suggested action63Error occurs during data copy of Linux migration63Cause63Suggested action63SAN-connected destination server displays a blue screen63Suggested action63Out of memory error occurs on the application station during migration64Suggested action64Destination server boots with an invalid IP address64Cause64Suggested action64Windows server migration Source Agent or PINT remote deployment is intermittent and deployment fails with a General failure occurred error64Suggested action64Unable to detect HP FlexFabric 10Gb 2-port 554FLR-SFP+ Adapter configured as iSCSI disk in step 5 of migration wizard64Suggested action64HP Smart Array B320i controller name is not displayed64Suggested action65Unable to install Service Pack for ProLiant (SPP) on Windows 2008 SP2 operating system after successful migration65Suggested action65Linux migration to servers with iSCSI storage fails to boot65Suggested action:65Postmigration65Migration does not start after confirmation. The event log continuously displays Operation Migration waiting for connection to source65Suggested action65Destination server mouse and keyboard do not work after a Windows migration65Suggested action65USB mouse or keyboard drivers are not loaded after an X2P Windows migration66Cause66Suggested action66Mouse does not work on the iLO of the destination server after a Linux X2P migration67Suggested action67Mouse does not work on the destination ESX virtual machine after a V2V migration67Suggested action67Drive letters are not the same in the migrated virtual machine guest after migration67Suggested action67Drives do not appear on the migrated operating system68Suggested action68Mouse and keyboard do not work after a Microsoft Hyper-V virtual machine is migrated to a ProLiant server68Suggested action68Static IP address cannot be assigned on the destination server after migration68Suggested action68Virtual machine hosts Integrated Components that are not installed on the destination virtual machine after migration68Suggested action68Exclamation point (!) appears on the NIC adapter in Device Manager on the migrated virtual machine69Suggested action69Network adapter in the destination ESX virtual machine is not initialized after a V2V migration69Suggested action69Destination virtual machine fails to boot after X2V migration69Cause69Suggested action69During editing of the settings of guest VMs created by server migration, an invalid OS ID warning appears69Suggested action69Server is unresponsive during PSP installation70Suggested action70Destination server still shows server migration UI but server migration wizard shows migration completed70Suggested action70Operating system is not booting on a destination server that has SAN disks70Suggested action70Error is displayed for a missing file system while migrated Linux OS is booted on the destination server70Suggested action70Logical drives of HP Smart Array B110i SATA RAID Controller are removed70Suggested action70Unable to download the log files from the migration wizard when using IE 971Suggested action71Microsoft Windows 2008 R2 SP1 does not boot on ProLiant BL420c Gen8 with Emulex LPe1205A FC storage controller.71Suggested action71Source server with SLES 11 SP2 x32 OS does not boot the operating system properly after successful migration71Suggested action71RHEL version 6.3 (x64) operating system does not boot after migrating to HP Dynamic Smart Array B120i/B320i Controllers71Suggested action71RHEL version 6.3 (x64) operating system does not boot as destination after successful migration71Suggested action7211 Support and other resources73Information to collect before contacting HP73How to contact HP73Security bulletin and alert policy for non-HP owned software components73Subscription service73Registering for software technical support and update service73How to use your software technical support and update service74HP authorized resellers74Related information74Documents74Websites74Related documentation75Typographic conventions7512 Documentation feedback77A Applying old server migration standalone licenses78B Performing migrations in a Microsoft Cluster server environment79Premigration consideration steps for clusters79Performing the migration80Post migration considerations and steps80C Logging server migration application service Logs into Windows NT Events82Glossary83Index84크기: 2.25메가바이트페이지: 87Language: English매뉴얼 열기