HP Insight Control User Manual
Insight control server migration, User guide
Advertising
Table of contents
Document Outline
- Insight Control server migration
- Table of Contents
- 1 Introduction
- Insight Control server migration
- Insight Control server migration benefits
- Insight Control server migration platform support
- Insight Control server migration components
- Planning a migration strategy
- Upgrading to Insight Control server migration from Insight Server Migration software for ProLiant
- Downgrading to Insight Server Migration software for ProLiant from Insight Control server migration
- Hardware and operating system support
- Configuration planning
- License verification
- Schedule preparation
- Memory and CPU resources on the application station
- Critical or hardware-dependent application preparation
- Virtual machine guest tools
- Domain controllers
- Microsoft Small Business Server
- Firewalls
- Antivirus software
- Dual-boot
- Resizing NTFS volumes for Windows migration
- File system selection for a Linux source server
- ProLiant Support Pack
- Linux ProLiant Support Pack
- Related HP products
- 2 Insight Control server migration installation and configuration requirements
- Insight Control server migration application station and Insight Control CMS
- Windows source servers
- Linux source servers
- Physical destination servers
- Virtual machine hosts
- Installing Insight Control server migration on the application station
- Changing the default Insight Control server migration application station service port number
- 3 Deploying migration agents
- Deploying server migration Source Agents
- Migration agents
- Insight Control server migration Boot CDs
- Using the Insight Control CMS to deploy the migration agent
- Using the application station to deploy the migration agent
- Using the application station to deploy the PINT agent
- Manually running server migration Source Agent on the source server
- Restarting the migration agent
- Booting the destination server for P2P, V2P, and X2V migrations
- Manually booting a physical destination server using the Insight Control server migration Boot CD for P2P and V2P
- Booting a destination server using the Insight Control Migration Wizard
- Manually creating and booting a virtual machine for Insight Control
- Automatically creating and booting a virtual destination server using the Insight Control Migration Wizard for P2V or V2V
- Configure Boot CD to launch destination agent
- HP Insight Server Migration software for ProLiant Overview screen
- Deploying server migration Source Agents
- 4 Licensing HP Insight Control server migration
- 5 Using Insight Control server migration to migrate servers
- Concurrent migrations
- Migration Wizard page
- Physical-to-ProLiant (P2P) migrations for Windows
- Physical-to-ProLiant (P2P) migrations for Linux
- Physical-to-virtual (P2V) migrations for Windows
- Physical-to-virtual (P2V) migrations for Linux
- Virtual-to-ProLiant (V2P) migrations for Windows
- Virtual-to-ProLiant (V2P) migrations for Linux
- Virtual-to-virtual (V2V) migrations for Windows
- Virtual-to-virtual (V2V) migrations for Linux
- SAN migrations
- Insight Control server migration application integration to Systems Insight Manager
- Quick Launch details
- 6 Viewing migration logs
- 7 Uploading drivers
- 8 Troubleshooting
- Installation
- When launching the HP Insight Control server migration wizard immediately after installation, the message Unable to communicate with the HP Insight Control server migration service appears on the wizard page
- Insight Control installation displays The Insight Server Migration software for ProLiant cannot be installed on a machine with an empty or invalid credentials error
- Insight Control related menus missing after installing Systems Insight Manager on Insight Control
- Insight Control related menus missing
- Support for older versions of standalone P2P application
- Configuration
- Source preparation
- Corrective action is required before migrating some preinstalled HP Microsoft Windows Server 2003 operating systems
- Corrective action is required for some source servers with HP Insight Control remote management Channel Interface Drivers
- Source server identification fails
- Migration agent deployment fails
- Server migration Source Agent deployment fails remotely from a Windows Server 2003 Application Station
- Remote deployment of Linux source agent using non-root credentials fails
- Linux server migration Source Agent deployment from a Windows 2003 Application station to a SLES 10 SP2 source server fails
- Incorrect LUN size detected in step 2 of the Migration Wizard
- Migrating a source server with the Microsoft Hyper-V role enabled
- Remote deployment of Linux source agent using non-root credentials fails
- Manual installation of Linux source agent using sudo user privileges fails
- Destination preparation
- Destination server identification fails
- Application station fails to connect to the destination server
- IP address configuration fails on a manually booted virtual machine in Microsoft Hyper-V for a P2V or a V2V migration
- Kernel panic occurs when booting a virtual machine to the Insight Control server migration Virtual Machine Boot CD
- Mouse does not work on a virtual machine booted with the Insight Control server migration Virtual Machine Boot CD
- Primary array controller does not have logical drives defined
- Primary controller configured in the system does not have drives attached
- Primary controller in system is not supported by this version of Insight Control
- Insight Control server migration Boot CD might stop responding when exiting the Array Configuration Utility
- 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
- Supported storage controllers display Unknown on the Boot CD
- Auto booting destination server using Insight Control remote management fails
- Insight Control might not detect virtual machines on mapped network drives
- Destination server boots from the Insight Control server migration Boot CD on a manual boot
- Destination server does not boot when automatic booting option was chosen during X2P migration wizard
- Destination server fails to boot while loading initrd.img
- Insight Control server migration stops responding during auto-booting of Microsoft Hyper-V virtual machine
- Application station fails to connect to the destination server when the server is auto-booted for a P2P or V2P migration
- ProLiant Boot CD may fail to detect the storage controller on a destination server
- Migration process
- Drivers cannot be installed or injected onto boot disk
- Large volumes fail with server thread error
- Migration fails to terminate if source server is shut down
- NTFS resize error message
- Migration fails during the disk cloning phase
- Migration fails with error Failed: Drivers Could Not Be Injected Into Boot Disk in the logs
- Insight Control cannot perform V2V migrations on virtual machine guests with certain disk types
- Destination VM not powered off on HP integrated Citrix XenServers
- 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 during data copy of Linux migration
- Destination server reboots continuously with a blue screen
- SAN-connected destination server displays blue screen
- Windows 2000 Advanced Server SP4 SAN migration displays blue screen on destination server with Emulex LPe1105-HP 4Gb FC HBA
- Systems Insight Manager rediscovery task is not triggered after a P2V migration
- 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 fails with Agent is already deployed or not required error
- Windows server migration Source Agent or PINT remote deployment is intermittent and deployment fails with General failure occured error
- Post-migration
- Destination server connected to SAN displays a blue screen after boot
- 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
- DNS error appears in the destination server after migration of domain controller
- 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 migrating a Microsoft Hyper-V virtual machine to a ProLiant server
- Static IP address cannot be assigned on the destination server after migration
- Virtual machine hosts Integrated Components do not install on the destination virtual machine following migration
- Yellow bang (!) 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
- Server is unresponsive during PSP installation
- Uninstallation
- Installation
- 9 Support and other resources
- A Portable Images Network Tool (PINT)
- Glossary
- Index