Document Outline

• HP Insight Control Server Migration 7.3 Update 1 User Guide
• Part I Overview and concepts
  • 1 Server migration introduction
    • Overview
    • Installing and configuring server migration software
      • Installing or upgrading server migration software
      • Licensing server migration
    • Related products
  • 2 Server migration concepts
    • Server migration components
    • Overview of migrating a server
      • Migration checklist
    • HP Insight Control server migration software tabs
• Part II Premigration tasks
  • 3 Preparing hardware for migration
    • Verifying hardware and operating system support
    • Verifying system requirements for the application station
  • 4 Planning the migration
    • Planning a migration strategy
    • Preparing a schedule
    • Considerations for multiboot systems
    • Migrating large NTFS partitions
    • Resizing file systems for migration
      • Resizing Windows file systems
      • Resizing Linux file systems
    • Manually disabling critical or hardware-dependent applications
  • 5 Preparing software for migration
    • Verifying licenses for software to be migrated
    • Migration security
      • Disabling firewalls
      • Disabling antivirus software
      • Generating static or dynamic certificates
    • Installing ProLiant Support Packs
    • Installing Service Pack for ProLiant
• Part III Migration
  • 6 Preparing the source server and deploying the Source Agent
    • Verifying Windows source server requirements
      • Preparing a Microsoft Hyper-V source server
    • Verifying Linux source server requirements
    • Removing guest tools
    • Choosing server migration Agents
    • Deploying server migration Agents
      • Deploying Agents
    • Manually running server migration Source Agents on the source server
      • Deploying a Windows server migration Source Agent locally on the source server
        • Deploying a server migration Source Agent on domain controllers
      • Deploying the Linux server migration Source Agent locally 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
      • Physical destination servers
      • Virtual machine hosts
    • 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
        • iLO boot prerequisites
      • Manually creating and booting a virtual destination server
        • Prerequisites for manually creating and booting a destination virtual machine
          • Prerequisites for booting a virtual machine in Microsoft Hyper-V
          • Prerequisites for VMware ESX migration
        • Manually creating and booting a virtual machine destination server for X2V
      • Automatically creating and booting a virtual destination server
  • 8 Migrating the servers
    • Prerequisites
      • Minimum source server prerequisites for all migrations
        • Uploading drivers
      • Preparing for a Windows server migration
        • Windows source server prerequisites
        • Source physical server prerequisites
        • Source virtual machine prerequisites
        • Destination physical server prerequisites
        • Destination virtual machine host or virtual machine prerequisites
      • Preparing for a Linux server migration
        • Source physical server prerequisites
        • Source virtual machine prerequisites
        • Destination physical server prerequisites
        • Destination virtual machine host or virtual machine prerequisites
      • SAN migrations in Windows
    • Starting the migration wizard
      • Launching server migration by using the Deploy menu
      • Launching server migration by using Quick Launch
  • 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
      • Validating Linux migrations
      • Validating Windows migrations
• Part IV Troubleshooting and support
  • 10 Troubleshooting
    • User interface
      • Server migration wizard hangs
        • Cause
        • Suggested action
      • Browser displays an error after loading the server migration wizard from Systems Insight Manager
        • Cause
        • Suggested action
      • Launching server migration from Systems Insight Manager throws an exception
        • Cause
        • Suggested action
      • The name of HP Ethernet 1Gb 4-port 331i-SPI Adapter is not displayed correctly
        • Suggested action
      • Unable to launch server migration tools from Systems Insight Manager
        • Suggested Action
      • Static IP configuration fails on Hyper-V VM when configured using Boot CD
        • Cause
          • Suggested action:
      • Unable to migrate Windows 2008/2008 R2/2012 R2
        • Cause
        • Suggested Action
    • Source preparation
      • Corrective action is required before this server can be migrated
        • Cause
        • Suggested action
      • Source server identification fails
        • Suggested action
      • Migration Agent deployment fails
        • Suggested action
      • Linux Source Agent window does not appear on RHEL 64–bit
        • Suggested action
      • Remote deployment of Linux Source Agent using nonroot credentials fails
        • Suggested action
        • Manual installation of Linux Source Agent using sudo user privileges fails
          • Suggested action
      • Incorrect LUN size is detected in step 2 of the migration wizard
        • Cause
        • Suggested action
      • Migrating a source server fails with the Microsoft Hyper-V role enabled
        • Suggested action
    • Destination preparation
      • Destination server identification fails
        • Suggested action
      • IP address configuration fails on a manually booted virtual machine in Microsoft Hyper-V for a P2V or V2V migration
        • Suggested action
      • Kernel panic occurs in booting a virtual machine to the Insight Control server migration Virtual Machine Boot CD ISO
        • Suggested action
      • Mouse does not work on a virtual machine booted with the Insight Control server migration Virtual Machine Boot CD ISO
        • Cause
        • Suggested action
      • Primary array controller does not have logical drives defined
        • Suggested action
      • Primary controller configured in the system does not have drives attached
        • Suggested action
      • Primary controller in the system is not supported by this version of Insight Control server migration
        • Suggested action
      • Destination server displays a blank screen when it boots to server migration Boot CD ISO
        • Suggested action
      • Some storage volumes on the destination server are not available for selection
        • Suggested action
      • Static IP address cannot be assigned on the destination server while booting using the Boot CD ISO
        • Cause
        • Suggested action
      • Supported storage controllers display Unknown on the Boot CD ISO
        • Cause
        • Suggested action
      • Automatic booting of the destination physical server fails
        • Suggested action
      • Insight Control server migration might not detect virtual machines on mapped network drives
        • Cause
        • Suggested action
      • Destination server does not boot even though the automatic booting option was chosen during X2P migrations
        • Suggested action
      • Insight Control server migration stops responding during automatic booting of Microsoft Hyper-V virtual machine
        • Suggested action
      • Application station fails to connect to the destination server when the server is automatically booted for an X2P migration
        • Cause
        • Suggested action
      • Warning message is not displayed for an unsupported server when the server is started using the Insight Control server migration ProLiant Boot CD
        • Suggested action
      • Microsoft Windows 2008 OS migration results in a blue screen error on destination server configured with NC551m FCoE card
        • Suggested action
    • Migration process
      • Drivers cannot be installed or injected onto a boot disk
        • Suggested action
      • Migrating a Linux source server that has large storage fails when the migration is initiated
        • Suggested action
      • Linux migration might fail when X Windows configuration is not properly formatted
        • Suggested action
      • Partitions created with third-party partitioning tools do not show the proper file system type in the server migration wizard
        • Suggested action
      • Migration hangs if the source server is shut down
        • Suggested action
      • NTFS resize error message appears
        • Cause
        • Suggested action
      • ReiserFS volumes are blocked for Linux migration
        • Cause
        • Suggested action
      • Filesystem on source disk \\.\PhysicalDrive0, Partition 0 could not be resized during the migration
        • Cause
        • Suggested action
      • Migration fails during the disk cloning phase
        • Cause
        • Suggested action
      • Starting a new migration after a current migration is stopped
        • Suggested action
      • Unrecoverable sector-read errors on the source server hard drive are not supported and fail a Windows P2P or P2V migration
        • Cause
        • Suggested action
      • Source Agent fails to launch when source server reboots in migration agent mode
        • Suggested action
      • Error occurs during data copy of Linux migration
        • Cause
        • Suggested action
      • SAN-connected destination server displays a blue screen
        • Suggested action
      • Out of memory error occurs on the application station during migration
        • Suggested action
      • Destination server boots with an invalid IP address
        • Cause
        • Suggested action
      • Windows server migration Source Agent or PINT remote deployment is intermittent and deployment fails with a General failure occurred error
        • Suggested action
      • Unable to detect HP FlexFabric 10Gb 2-port 554FLR-SFP+ Adapter configured as iSCSI disk in step 5 of migration wizard
        • Suggested action
      • Unable to install Service Pack for ProLiant (SPP) on Windows Operating System after successful migration or Yellow bangs (!) are seen in the device manager on reboot.
        • Suggested action
    • Postmigration
      • Migration of Windows 2008 SP2 to Smart Array controllers, destination server results in blue screen error.
        • Suggested Action
      • Migration of Windows 2008 or Windows 2012 from Physical Server—> Physical Server—> Physical Server, results in blue screen error.
        • Suggested action
      • Migration does not start after confirmation. The event log continuously displays Operation Migration waiting for connection to source
        • Suggested action
      • Destination server mouse and keyboard do not work after a Windows migration
        • Suggested action
      • USB mouse or keyboard drivers are not loaded after an X2P Windows migration
        • Cause
        • Suggested action
      • Mouse does not work on the iLO of the destination server after a Linux X2P migration
        • Suggested action
      • Mouse does not work on the destination ESX virtual machine after a V2V migration
        • Suggested action
      • Drive letters are not the same in the migrated virtual machine guest after migration
        • Suggested action
      • Drives do not appear on the migrated operating system
        • Suggested action
      • Mouse and keyboard do not work after a Microsoft Hyper-V virtual machine is migrated to a ProLiant server
        • Suggested action
      • Static IP address cannot be assigned on the destination server after migration
        • Suggested action
      • Virtual machine hosts Integrated Components that are not installed on the destination virtual machine after migration
        • Suggested action
      • Exclamation point (!) appears on the NIC adapter in Device Manager on the migrated virtual machine
        • Suggested action
      • Network adapter in the destination ESX virtual machine is not initialized after a V2V migration
        • Suggested action
      • Destination virtual machine fails to boot after X2V migration
        • Cause
        • Suggested action
      • During editing of the settings of guest VMs created by server migration, an invalid OS ID warning appears
        • Suggested action
      • Server is unresponsive during PSP installation
        • Suggested action
      • Destination server still shows server migration UI but server migration wizard shows migration completed
        • Suggested action
      • Operating system is not booting on a destination server that has SAN disks
        • Suggested action
      • Post Migration of SLES 11 SP3 OS boot up takes long time on destination server with Brocade 82B or 41B or SN1000Q FC card
        • Suggested action
      • Error is displayed for a missing file system while migrated Linux OS is booted on the destination server
        • Suggested action
      • Logical drives of HP Smart Array B110i SATA RAID Controller are removed
        • Suggested action
      • Unable to download the log files from the migration wizard when using IE 9
        • Suggested action
      • Source server with SLES 11 SP2 x32 OS does not boot the operating system properly after successful migration
        • Suggested action
      • RHEL version 6.3 (x64) operating system does not boot after migrating to HP Dynamic Smart Array B120i/B320i Controllers
        • Suggested action
      • RHEL version 6.5 (x64) operating system does not boot up on Smart Array P712 after successful migration.
        • Suggested action
      • RHEL version 6.3 (x64) operating system does not boot as destination after successful migration
        • Suggested action
    • Failed discovery logs and IP address not discovered.
      • Suggested Action
    • Post migration, RHEL 6.2 32 bit takes twenty minutes to boot from HP CN1000Q Dual Port Converged Network Adapter
      • Suggested Action
    • B120i controller is displayed as Intel Lynx storage controller
      • Suggested Action
  • 11 Support and other resources
    • Information to collect before contacting HP
    • How to contact HP
    • Security bulletin and alert policy for non-HP owned software components
    • Subscription service
    • Registering for software technical support and update service
      • How to use your software technical support and update service
    • HP authorized resellers
    • Related information
      • Documents
      • Websites
      • Related documentation
    • Typographic conventions
  • 12 Documentation feedback
• A Applying old server migration standalone licenses
• B Performing migrations in a Microsoft Cluster server environment
  • Premigration consideration steps for clusters
  • Performing the migration
  • Post migration considerations and steps
• C Logging server migration application service Logs into Windows NT Events
• Glossary
• Index