HP Insight Control Software for Linux User Manual
Hp insight control server migration 7.3 user guide
Advertising
This manual is related to the following products:
Table of contents
Document Outline
- HP Insight Control Server Migration 7.3 User Guide
- Part I Overview and concepts
- Part II Premigration tasks
- Part III Migration
- 6 Preparing the source server and deploying the Source Agent
- Verifying Windows source server requirements
- Verifying Linux source server requirements
- Removing guest tools
- Choosing server migration Agents
- Deploying server migration Agents
- Manually running server migration Source Agents on the source server
- Detecting, stopping, or restarting a remotely deployed server migration Source Agent
- 7 Preparing the destination server and deploying the destination agent
- Prerequisites
- Linux destination size requirement
- Booting the destination server
- Booting a physical destination server manually by using the Insight Control server migration ProLiant Boot CD ISO for X2P migrations
- Booting a physical destination server automatically by using the migration wizard
- Manually creating and booting a virtual destination server
- Automatically creating and booting a virtual destination server
- 8 Migrating the servers
- 9 Postmigration tasks
- Installing ProLiant Support Packs after migration
- Installing Service Pack for ProLiant after migration
- X2P postmigration tasks (Windows)
- X2V postmigration tasks (Windows)
- Editing the Windows boot.ini file after migration (Windows Server 2003)
- X2P postmigration tasks (Linux)
- X2V postmigration tasks (Linux)
- Viewing migration logs
- Validating the migration
- 6 Preparing the source server and deploying the Source Agent
- Part IV Troubleshooting and support
- 10 Troubleshooting
- User interface
- Server migration wizard hangs
- Browser displays an error after loading the server migration wizard from Systems Insight Manager
- Launching server migration from Systems Insight Manager throws an exception
- The name of HP Ethernet 1Gb 4-port 331i-SPI Adapter is not displayed correctly
- Unable to launch server migration tools from Systems Insight Manager
- Static IP configuration fails on Hyper-V VM when configured using Boot CD
- Unable to migrate Windows 2008/2008 R2/2012 R2
- Source preparation
- Corrective action is required before this server can be migrated
- Source server identification fails
- Migration Agent deployment fails
- Linux Source Agent window does not appear on RHEL 64–bit
- Remote deployment of Linux Source Agent using nonroot credentials fails
- Incorrect LUN size is detected in step 2 of the migration wizard
- Migrating a source server fails with the Microsoft Hyper-V role enabled
- Windows Migration agent successful, even when deployment fails
- Destination preparation
- Destination server identification fails
- IP address configuration fails on a manually booted virtual machine in Microsoft Hyper-V for a P2V or V2V migration
- Kernel panic occurs in booting a virtual machine to the Insight Control server migration Virtual Machine Boot CD ISO
- Mouse does not work on a virtual machine booted with the Insight Control server migration Virtual Machine Boot CD ISO
- Primary array controller does not have logical drives defined
- Primary controller configured in the system does not have drives attached
- Primary controller in the system is not supported by this version of Insight Control server migration
- Destination server displays a blank screen when it boots to server migration Boot CD ISO
- Some storage volumes on the destination server are not available for selection
- Static IP address cannot be assigned on the destination server while booting using the Boot CD ISO
- Supported storage controllers display Unknown on the Boot CD ISO
- Automatic booting of the destination physical server fails
- Insight Control server migration might not detect virtual machines on mapped network drives
- Destination server does not boot even though the automatic booting option was chosen during X2P migrations
- Insight Control server migration stops responding during automatic booting of Microsoft Hyper-V virtual machine
- Application station fails to connect to the destination server when the server is automatically booted for an X2P migration
- Warning message is not displayed for an unsupported server when the server is started using the Insight Control server migration ProLiant Boot CD
- Microsoft Windows 2008 OS migration results in a blue screen error on destination server configured with NC551m FCoE card
- Migration process
- Drivers cannot be installed or injected onto a boot disk
- Migrating a Linux source server that has large storage fails when the migration is initiated
- Linux migration might fail when X Windows configuration is not properly formatted
- Partitions created with third-party partitioning tools do not show the proper file system type in the server migration wizard
- Migration hangs if the source server is shut down
- NTFS resize error message appears
- ReiserFS volumes are blocked for Linux migration
- Filesystem on source disk \\.\PhysicalDrive0, Partition 0 could not be resized during the migration
- Migration fails during the disk cloning phase
- Failed: Drivers could Not Be Injected Into Boot Disk in the logs
- Starting a new migration after a current migration is stopped
- Unrecoverable sector-read errors on the source server hard drive are not supported and fail a Windows P2P or P2V migration
- Source Agent fails to launch when source server reboots in migration agent mode
- Error occurs during data copy of Linux migration
- SAN-connected destination server displays a blue screen
- Out of memory error occurs on the application station during migration
- Destination server boots with an invalid IP address
- Windows server migration Source Agent or PINT remote deployment is intermittent and deployment fails with a General failure occurred error
- Unable to detect HP FlexFabric 10Gb 2-port 554FLR-SFP+ Adapter configured as iSCSI disk in step 5 of migration wizard
- Unable to install Service Pack for ProLiant (SPP) on Windows Operating System after successful migration
- Linux migration to servers with iSCSI storage fails to boot
- Postmigration
- Migration does not start after confirmation. The event log continuously displays Operation Migration waiting for connection to source
- Destination server mouse and keyboard do not work after a Windows migration
- USB mouse or keyboard drivers are not loaded after an X2P Windows migration
- Mouse does not work on the iLO of the destination server after a Linux X2P migration
- Mouse does not work on the destination ESX virtual machine after a V2V migration
- Drive letters are not the same in the migrated virtual machine guest after migration
- Drives do not appear on the migrated operating system
- Mouse and keyboard do not work after a Microsoft Hyper-V virtual machine is migrated to a ProLiant server
- Static IP address cannot be assigned on the destination server after migration
- Virtual machine hosts Integrated Components that are not installed on the destination virtual machine after migration
- Exclamation point (!) appears on the NIC adapter in Device Manager on the migrated virtual machine
- Network adapter in the destination ESX virtual machine is not initialized after a V2V migration
- Destination virtual machine fails to boot after X2V migration
- During editing of the settings of guest VMs created by server migration, an invalid OS ID warning appears
- Server is unresponsive during PSP installation
- Destination server still shows server migration UI but server migration wizard shows migration completed
- Operating system is not booting on a destination server that has SAN disks
- Error is displayed for a missing file system while migrated Linux OS is booted on the destination server
- Logical drives of HP Smart Array B110i SATA RAID Controller are removed
- Unable to download the log files from the migration wizard when using IE 9
- Microsoft Windows 2008 R2 SP1 does not boot on ProLiant BL420c Gen8 with Emulex LPe1205A FC storage controller.
- Source server with SLES 11 SP2 x32 OS does not boot the operating system properly after successful migration
- RHEL version 6.3 (x64) operating system does not boot after migrating to HP Dynamic Smart Array B120i/B320i Controllers
- RHEL version 6.3 (x64) operating system does not boot as destination after successful migration
- Failed discovery logs and IP address not discovered.
- Post migration, RHEL 6.2 32 bit takes twenty minutes to boot from HP CN1000Q Dual Port Converged Network Adapter
- B120i controller is displayed as Intel Lynx storage controller
- User interface
- 11 Support and other resources
- 12 Documentation feedback
- 10 Troubleshooting
- A Applying old server migration standalone licenses
- B Performing migrations in a Microsoft Cluster server environment
- C Logging server migration application service Logs into Windows NT Events
- Glossary
- Index