HP (Hewlett-Packard) Insight Control Server Migration User Manual
HP Insight Control Server Migration 7.2 User Guide
Abstract
HP Insight Control server migration provides an automated, accurate, and affordable way to migrate existing servers to the
latest HP ProLiant server technologies or the latest virtualization platforms. This guide explains processes and procedures that
are not appropriate for the product's online help. The information in this guide is intended for users who have network
administrator–level access and knowledge.
HP Part Number: 461487-401a
Published: June 2013
Edition: 2
© Copyright 2007, 2013 Hewlett-Packard Development Company, L.P.
Legal Notices
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Acknowledgements
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Java is a registered trademark of Oracle Corporation and/or its affiliates.
Intel®, Itanium®, and Intel® Xeon® are registered trademarks of the Intel Corporation in the United States and other countries.
Warranty
HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty applies to all Insight Management
products.
Contents
I Overview and concepts..............................................................................10
1 Server migration introduction..................................................................11
Overview..........................................................................................................................11
Installing and configuring server migration software...............................................................11
Installing or upgrading server migration software..............................................................11
Licensing server migration..............................................................................................11
Related products................................................................................................................11
2 Server migration concepts......................................................................13
Server migration components..............................................................................................13
Overview of migrating a server............................................................................................13
Migration checklist........................................................................................................13
HP Insight Control server migration software tabs...................................................................14
II Premigration tasks.....................................................................................16
3 Preparing hardware for migration...........................................................17
Verifying hardware and operating system support..................................................................17
Verifying system requirements for the application station..........................................................17
4 Planning the migration...........................................................................18
Planning a migration strategy..............................................................................................18
Preparing a schedule..........................................................................................................18
Considerations for multiboot systems.....................................................................................18
Migrating large NTFS partitions...........................................................................................18
Resizing file systems for migration........................................................................................18
Resizing Windows file systems........................................................................................18
Resizing Linux file systems...............................................................................................19
Manually disabling critical or hardware-dependent applications..............................................19
5 Preparing software for migration.............................................................20
Verifying licenses for software to be migrated........................................................................20
Migration security..............................................................................................................20
Disabling firewalls.........................................................................................................20
Disabling antivirus software............................................................................................21
Generating static or dynamic certificates..........................................................................21
Installing ProLiant Support Packs..........................................................................................21
Installing Service Pack for ProLiant........................................................................................21
III Migration................................................................................................23
6 Preparing the source server and deploying the Source Agent......................24
Verifying Windows source server requirements.......................................................................24
Preparing a Microsoft Hyper-V source server.....................................................................24
Verifying Linux source server requirements.............................................................................24
Removing guest tools..........................................................................................................25
Choosing server migration Agents........................................................................................25
Deploying server migration Agents.......................................................................................25
Deploying Agents..........................................................................................................25
Manually running server migration Source Agents on the source server.....................................26
Deploying a Windows server migration Source Agent locally on the source server.................26
Deploying a server migration Source Agent on domain controllers..................................28
Deploying the Linux server migration Source Agent locally on the source server.....................28
Detecting, stopping, or restarting a remotely deployed server migration Source Agent.................29
Contents 3
7 Preparing the destination server and deploying the destination agent..........30
Prerequisites......................................................................................................................30
Physical destination servers.............................................................................................30
Virtual machine hosts.....................................................................................................30
Linux destination size requirement........................................................................................30
Booting the destination server..............................................................................................31
Booting a physical destination server manually by using the Insight Control server migration
ProLiant Boot CD ISO for X2P migrations..........................................................................31
Booting a physical destination server automatically by using the migration wizard.................32
iLO boot prerequisites...............................................................................................32
Manually creating and booting a virtual destination server.................................................32
Prerequisites for manually creating and booting a destination virtual machine..................32
Prerequisites for booting a virtual machine in Microsoft Hyper-V.................................32
Prerequisites for VMware ESX migration..................................................................33
Manually creating and booting a virtual machine destination server for X2V....................33
Automatically creating and booting a virtual destination server...........................................33
8 Migrating the servers............................................................................35
Prerequisites......................................................................................................................35
Minimum source server prerequisites for all migrations.......................................................35
Uploading drivers.....................................................................................................35
Preparing for a Windows server migration.......................................................................36
Windows source server prerequisites...........................................................................36
Source physical server prerequisites............................................................................36
Source virtual machine prerequisites...........................................................................37
Destination physical server prerequisites......................................................................37
Destination virtual machine host or virtual machine prerequisites.....................................37
Preparing for a Linux server migration..............................................................................37
Source physical server prerequisites............................................................................38
Source virtual machine prerequisites...........................................................................38
Destination physical server prerequisites......................................................................38
Destination virtual machine host or virtual machine prerequisites.....................................39
SAN migrations in Windows..........................................................................................39
Starting the migration wizard...............................................................................................40
Launching server migration by using the Deploy menu........................................................40
Launching server migration by using Quick Launch............................................................41
9 Postmigration tasks................................................................................44
Installing ProLiant Support Packs after migration.....................................................................44
Installing Service Pack for ProLiant after migration..................................................................44
X2P postmigration tasks (Windows)......................................................................................44
X2V postmigration tasks (Windows).....................................................................................45
Editing the Windows boot.ini file after migration (Windows Server 2003).................................45
X2P postmigration tasks (Linux)............................................................................................46
X2V postmigration tasks (Linux)............................................................................................46
Viewing migration logs.......................................................................................................47
Validating the migration.....................................................................................................47
Validating Linux migrations.............................................................................................47
Validating Windows migrations......................................................................................47
IV Troubleshooting and support.....................................................................48
10 Troubleshooting..................................................................................49
User interface....................................................................................................................49
Server migration wizard hangs........................................................................................49
Cause.....................................................................................................................49
Suggested action......................................................................................................49
4 Contents
Browser displays an error after loading the server migration wizard from Systems Insight
Manager.....................................................................................................................49
Cause.....................................................................................................................49
Suggested action......................................................................................................49
Launching server migration from Systems Insight Manager throws an exception.....................49
Cause.....................................................................................................................49
Suggested action......................................................................................................49
The name of HP Ethernet 1Gb 4-port 331i-SPI Adapter is not displayed correctly...................49
Suggested action......................................................................................................50
Unable to launch server migration tools from Systems Insight Manager.................................50
Suggested Action.....................................................................................................50
Static IP configuration fails on Hyper-V VM when configured using Boot CD..........................50
Cause.....................................................................................................................50
Suggested action:................................................................................................50
Unable to migrate Windows 2008/2008 R2/2012 using Windows 2008 x64 CMS............50
Cause ....................................................................................................................50
Suggested Action ....................................................................................................50
Source preparation............................................................................................................51
Corrective action is required before this server can be migrated..........................................51
Cause.....................................................................................................................51
Suggested action......................................................................................................51
Source server identification fails......................................................................................51
Suggested action......................................................................................................51
Migration Agent deployment fails....................................................................................52
Suggested action......................................................................................................52
Linux Source Agent window does not appear on RHEL 64–bit.............................................52
Suggested action......................................................................................................53
Remote deployment of Linux Source Agent using nonroot credentials fails.............................53
Suggested action......................................................................................................53
Manual installation of Linux Source Agent using sudo user privileges fails........................53
Suggested action.................................................................................................53
Incorrect LUN size is detected in step 2 of the migration wizard...........................................53
Cause.....................................................................................................................53
Suggested action......................................................................................................53
Migrating a source server fails with the Microsoft Hyper-V role enabled................................53
Suggested action......................................................................................................53
Unable to boot Windows due to unsigned or corrupt drivers...............................................54
Suggested action......................................................................................................54
Destination preparation......................................................................................................54
Destination server identification fails................................................................................54
Suggested action......................................................................................................54
IP address configuration fails on a manually booted virtual machine in Microsoft Hyper-V for
a P2V or V2V migration.................................................................................................54
Suggested action......................................................................................................54
Kernel panic occurs in booting a virtual machine to the Insight Control server migration Virtual
Machine Boot CD ISO...................................................................................................54
Suggested action......................................................................................................55
Mouse does not work on a virtual machine booted with the Insight Control server migration
Virtual Machine Boot CD ISO.........................................................................................55
Cause.....................................................................................................................55
Suggested action......................................................................................................55
Primary array controller does not have logical drives defined..............................................55
Suggested action......................................................................................................55
Primary controller configured in the system does not have drives attached.............................55
Suggested action......................................................................................................55
Contents 5
Primary controller in the system is not supported by this version of Insight Control server
migration.....................................................................................................................55
Suggested action......................................................................................................55
Destination server displays a blank screen when it boots to server migration Boot CD ISO......56
Suggested action......................................................................................................56
Some storage volumes on the destination server are not available for selection......................56
Suggested action......................................................................................................56
Static IP address cannot be assigned on the destination server while booting using the Boot
CD ISO........................................................................................................................56
Cause.....................................................................................................................56
Suggested action......................................................................................................57
Supported storage controllers display Unknown on the Boot CD ISO....................................57
Cause.....................................................................................................................57
Suggested action......................................................................................................57
Automatic booting of the destination physical server fails....................................................57
Suggested action......................................................................................................57
3 Insight Control server migration might not detect virtual machines on mapped network
drives..........................................................................................................................57
Cause.....................................................................................................................57
Suggested action......................................................................................................57
Destination server does not boot even though the automatic booting option was chosen during
X2P migrations.............................................................................................................57
Suggested action......................................................................................................57
Insight Control server migration stops responding during automatic booting of Microsoft Hyper-V
virtual machine.............................................................................................................58
Suggested action......................................................................................................58
Application station fails to connect to the destination server when the server is automatically
booted for an X2P migration...........................................................................................58
Cause.....................................................................................................................58
Suggested action......................................................................................................58
Warning message is not displayed for an unsupported server when the server is started using
the Insight Control server migration ProLiant Boot CD.........................................................58
Suggested action......................................................................................................58
Microsoft Windows 2008 OS migration results in a blue screen error on destination server
configured with NC551m FCoE card...............................................................................58
Suggested action......................................................................................................59
Migration process..............................................................................................................59
Drivers cannot be installed or injected onto a boot disk......................................................59
Suggested action......................................................................................................59
Large volumes fail with a server thread error.....................................................................59
Suggested action......................................................................................................59
Migrating a Linux source server that has large storage fails when the migration is initiated......59
Suggested action......................................................................................................59
Linux migration might fail when X Windows configuration is not properly formatted...............60
Suggested action......................................................................................................60
Partitions created with third-party partitioning tools do not show the proper file system type in
the server migration wizard............................................................................................60
Suggested action......................................................................................................60
Migration hangs if the source server is shut down..............................................................60
Suggested action......................................................................................................60
NTFS resize error message appears.................................................................................61
Cause.....................................................................................................................61
Suggested action......................................................................................................61
ReiserFS volumes are blocked for Linux migration...............................................................61
Cause.....................................................................................................................61
6 Contents
Suggested action......................................................................................................61
Filesystem on source disk \\.\PhysicalDrive0, Partition 0 could not be resized during the
migration.....................................................................................................................61
Cause.....................................................................................................................61
Suggested action......................................................................................................62
Migration fails during the disk cloning phase....................................................................62
Cause.....................................................................................................................62
Suggested action......................................................................................................62
Failed: Drivers could Not Be Injected Into Boot Disk in the logs............................................62
Suggested action......................................................................................................62
Starting a new migration after a current migration is stopped..............................................62
Suggested action......................................................................................................62
Unrecoverable sector-read errors on the source server hard drive are not supported and fail
a Windows P2P or P2V migration...................................................................................62
Cause.....................................................................................................................63
Suggested action......................................................................................................63
Source Agent fails to launch when source server reboots in migration agent mode.................63
Suggested action......................................................................................................63
Error occurs during data copy of Linux migration...............................................................63
Cause.....................................................................................................................63
Suggested action......................................................................................................63
SAN-connected destination server displays a blue screen...................................................63
Suggested action......................................................................................................63
Out of memory error occurs on the application station during migration...............................64
Suggested action......................................................................................................64
Destination server boots with an invalid IP address............................................................64
Cause.....................................................................................................................64
Suggested action......................................................................................................64
Windows server migration Source Agent or PINT remote deployment is intermittent and
deployment fails with a General failure occurred error.......................................................64
Suggested action......................................................................................................64
Unable to detect HP FlexFabric 10Gb 2-port 554FLR-SFP+ Adapter configured as iSCSI disk
in step 5 of migration wizard..........................................................................................64
Suggested action......................................................................................................64
HP Smart Array B320i controller name is not displayed......................................................64
Suggested action......................................................................................................65
Unable to install Service Pack for ProLiant (SPP) on Windows 2008 SP2 operating system after
successful migration.......................................................................................................65
Suggested action......................................................................................................65
Linux migration to servers with iSCSI storage fails to boot ..................................................65
Suggested action: ....................................................................................................65
Postmigration ....................................................................................................................65
Migration does not start after confirmation. The event log continuously displays Operation
Migration waiting for connection to source.......................................................................65
Suggested action......................................................................................................65
Destination server mouse and keyboard do not work after a Windows migration...................65
Suggested action......................................................................................................65
USB mouse or keyboard drivers are not loaded after an X2P Windows migration..................66
Cause.....................................................................................................................66
Suggested action......................................................................................................66
Mouse does not work on the iLO of the destination server after a Linux X2P migration............67
Suggested action......................................................................................................67
Mouse does not work on the destination ESX virtual machine after a V2V migration...............67
Suggested action......................................................................................................67
Drive letters are not the same in the migrated virtual machine guest after migration................67
Contents 7
Suggested action......................................................................................................67
Drives do not appear on the migrated operating system.....................................................68
Suggested action......................................................................................................68
Mouse and keyboard do not work after a Microsoft Hyper-V virtual machine is migrated to a
ProLiant server..............................................................................................................68
Suggested action......................................................................................................68
Static IP address cannot be assigned on the destination server after migration.......................68
Suggested action......................................................................................................68
Virtual machine hosts Integrated Components that are not installed on the destination virtual
machine after migration.................................................................................................68
Suggested action......................................................................................................68
Exclamation point (!) appears on the NIC adapter in Device Manager on the migrated virtual
machine......................................................................................................................69
Suggested action......................................................................................................69
Network adapter in the destination ESX virtual machine is not initialized after a V2V
migration.....................................................................................................................69
Suggested action......................................................................................................69
Destination virtual machine fails to boot after X2V migration...............................................69
Cause.....................................................................................................................69
Suggested action......................................................................................................69
During editing of the settings of guest VMs created by server migration, an invalid OS ID
warning appears..........................................................................................................69
Suggested action......................................................................................................69
Server is unresponsive during PSP installation....................................................................70
Suggested action......................................................................................................70
Destination server still shows server migration UI but server migration wizard shows migration
completed....................................................................................................................70
Suggested action......................................................................................................70
Operating system is not booting on a destination server that has SAN disks..........................70
Suggested action......................................................................................................70
Error is displayed for a missing file system while migrated Linux OS is booted on the destination
server..........................................................................................................................70
Suggested action......................................................................................................70
Logical drives of HP Smart Array B110i SATA RAID Controller are removed ..........................70
Suggested action......................................................................................................70
Unable to download the log files from the migration wizard when using IE 9........................71
Suggested action......................................................................................................71
Microsoft Windows 2008 R2 SP1 does not boot on ProLiant BL420c Gen8 with Emulex
LPe1205A FC storage controller. .....................................................................................71
Suggested action......................................................................................................71
Source server with SLES 11 SP2 x32 OS does not boot the operating system properly after
successful migration.......................................................................................................71
Suggested action......................................................................................................71
RHEL version 6.3 (x64) operating system does not boot after migrating to HP Dynamic Smart
Array B120i/B320i Controllers.......................................................................................71
Suggested action......................................................................................................71
RHEL version 6.3 (x64) operating system does not boot as destination after successful
migration.....................................................................................................................71
Suggested action......................................................................................................72
11 Support and other resources.................................................................73
Information to collect before contacting HP............................................................................73
How to contact HP.............................................................................................................73
Security bulletin and alert policy for non-HP owned software components .................................73
Subscription service ...........................................................................................................73
8 Contents
Registering for software technical support and update service..................................................73
How to use your software technical support and update service..........................................74
HP authorized resellers.......................................................................................................74
Related information............................................................................................................74
Documents...................................................................................................................74
Websites......................................................................................................................74
Related documentation...................................................................................................75
Typographic conventions.....................................................................................................75
12 Documentation feedback......................................................................77
A Applying old server migration standalone licenses........................................78
B Performing migrations in a Microsoft Cluster server environment......................79
Premigration consideration steps for clusters...............................................................................79
Performing the migration..........................................................................................................80
Post migration considerations and steps.....................................................................................80
C Logging server migration application service Logs into Windows NT Events ....82
Glossary....................................................................................................83
Index.........................................................................................................84
Contents 9
Part I Overview and concepts
This part focuses on conceptual information that will help to understand the product. It does not include
information on how to use server migration.
1 Server migration introduction
Overview
HP Insight Control server migration provides an automated, accurate, and affordable way to
migrate existing servers running Microsoft Windows or Linux and their content to the latest HP
ProLiant server technologies or the latest virtualization platforms from VMware and Microsoft.
Insight Control server migration supports the following types of Microsoft Windows and Linux
migrations:
• Physical-to-ProLiant (P2P) migration—Migrates a physical machine to a ProLiant server.
• Physical-to-Virtual (P2V) migration—Migrates a physical machine to a virtual machine guest
in a virtual machine host.
• Virtual-to-ProLiant (V2P) migration—Migrates a virtual machine guest in a virtual machine host
to a ProLiant server.
• Virtual-to-Virtual (V2V) migration—Migrates a virtual machine guest between virtualization
layers.
Installing and configuring server migration software
Installing or upgrading server migration software
HP Insight Control server migration software is delivered on the HP Insight Management distribution
media and is installed through the Insight Management Integrated Installer. The server on which
you install Insight Management is designated to be the Central Management Server (CMS).
For installation and upgrade instructions and supported upgrade paths, see the HP Insight
Management Installation and Configuration Guide.
For a description of all software that is delivered on the Insight Management distribution media,
see the HP Insight Management Getting Started Guide.
Licensing server migration
The standard procedure for licensing Insight Control server migration is to purchase and apply
Insight Control licenses. So if your destination server is licensed by Insight Control version 6.0 or
later, you can perform unlimited migrations to the Insight Control licensed server.
For general licensing information, see the HP Insight Management Getting Started Guide, available
at the following website:
http://www.hp.com/go/insightmanagement
Related products
Table 1 (page 11) lists HP products that are available for extending deployment or customizing
the migrated server.
Table 1 Related products
HP Portable Images Network Tool (PINT) and HP Portable
Images Storage Assistant (PISA)
HP OpenView Change and Configuration Management
solutions
DescriptionProduct
Used to solve networking issues (specifically, NIC
configuration issues) in moving operating system images
between HP BladeSystem c-Class blades using VMware
ESX and Microsoft Hyper-V (for PINT only) virtual machines,
and HP Virtual Connect on HP BladeSystem c-Class blades.
Automates the management of software such as operating
systems, applications, patches, content, and configuration
Overview 11
Table 1 Related products (continued)
DescriptionProduct
settings, so that each computing device is maintained in
the right configuration.
Insight Control server deployment
HP SmartStart CD
HP SmartStart Scripting Toolkit
Facilitates the installation, configuration, and deployment
of large server volumes through a GUI-based or a
web–based console, using scripting or imaging technology.
Server configuration time decreases so that you can quickly
scale server deployments to large volumes.
Provides step-by-step ProLiant server deployment assistance.
From configuring arrays and installing operating systems,
to updating optimized ProLiant server support software,
SmartStart ensures a stable and reliable configuration.
Included in the HP ProLiant Essentials Foundation Pack, the
SmartStart CD works with all HP ProLiant DL and ML 300,
500, and 700 series, and all ProLiant BL servers.
A server deployment product that delivers unattended
automated installation for high-volume ProLiant server
installations.
Available in Windows and Linux editions, the toolkit
supports ProLiant DL and ML 300, 500, and 700 series,
and all ProLiant BL servers.
The toolkit includes a modular set of tools and important
documentation that describes how to apply these tools to
automate server deployment.
12 Server migration introduction
2 Server migration concepts
Server migration components
The Insight Control server migration environment consists of the following required components:
• Application station—The computer from which the migration is set up and performed. This
can be either a physical machine or a Windows guest on a supported hypervisor.
In earlier versions of HP Insight Management, the standalone installation of Insight Control
server migration software was enabled. The server on which the server migration software
was installed was then designated the application station. The installation of standalone server
migration software is no longer supported, and so the same server that hosts the installation
of Insight Management software and HP Systems Insight Manager now must host the Insight
Control server migration software. The terms “application station” and "CMS" now both refer
to the same server, which hosts both Insight Management and the server migration software.
• Source server—The physical source server or the virtual machine to be migrated.
• Destination server—The ProLiant server or the virtual machine to which the source server is
migrated.
Overview of migrating a server
Use the checklist in this section as a general guide to the tasks performed during a server migration.
For an explanation of the tabs in the server migration wizard, see “HP Insight Control server
migration software tabs” (page 14).
Migration checklist
The specific tasks required to complete a migration are listed in the server migration online help.
However, every migration can be condensed into the following general migration tasks:
1. Plan the migration.
2. Prepare the hardware and software for migration.
3. Prepare the source server or virtual machine for migration by installing the server migration
Source Agent on the source server or virtual machine:
a. Deploy the server migration Source Agent to the source server.
b. Select the source disks to migrate.
4. Prepare the destination server or virtual machine for migration:
a. Boot the destination server by using the Boot CD. For HP ProLiant Gen8 servers, only the
autoboot option is supported.
b. Create the destination disks.
5. Migrate the servers:
a. Test the network connectivity between the source and destination servers.
b. Map the source disks to the destination disks.
c. Choose destination server reboot, driver package, and network options.
d. Review choices and execute the migration.
6. Monitor the migration progress and view the logs when the migration is complete.
7. Log on to the new server and configure the drivers, communication settings, and boot options.
Server migration components 13
HP Insight Control server migration software tabs
Figure 1 Migration screen
The Insight Control server migration software screen has the following tabs:
• Migration Wizard
This tab enables you to perform the Insight Control server migration. In summary, the migration
wizard enables you to perform the following tasks:
◦ Identify the source server
◦ Select the volumes to migrate
◦ Identify the destination server
◦ Test the network connections
◦ Specify destination disks and resizing partitions
◦ Select additional migration options, as necessary
◦ Confirm and perform the migration
◦ Review migration progress
For more information about the migration wizard, see “Starting the migration wizard”
(page 40).
• View Status/Logs
This tab enables you to view the details and results of attempted migrations and to delete
migration results. For more information about viewing logs, see “Viewing migration logs”
(page 47).
14 Server migration concepts
• Upload Drivers
This tab displays the status of iSCSI Initiator and DISM installed on the server and provides
the option to upload HP ProLiant Support Pack (PSP) executable files and HP Service Pack for
ProLiant (SPP) ISO images. This tab also displays the installation status of DevCon and provides
the option to upload the DevCon binary. For more information about this tab, see “Uploading
drivers” (page 35).
• Deploy Agent
This tab enables you to deploy the Insight Control server migration Source Agent and PINT
Agents.
HP Insight Control server migration software tabs 15
Part II Premigration tasks
This part of the guide assists you in collecting information to prepare for a migration, and covers steps 1
and 2 of the checklist provided in “Migration checklist” (page 13).
3 Preparing hardware for migration
Verifying hardware and operating system support
Before you start any X2P (P2P or V2P) migration, verify the following:
• The source server operating system is supported on the destination server. To verify OS support
on ProLiant destination servers, see the following website:
http://www.hp.com/go/ossupport
• For the supported hardware and software configurations of server migration, see HP Insight
Management Support Matrix available at:
http://www.hp.com/go/insightmanagement/docs
Remove unsupported storage and NIC controllers from the destination server before you perform
a migration. Unsupported storage and NIC controllers can be added back on the destination
server, with proper manual configuration, after a migration.
Verifying system requirements for the application station
The application station has the following prerequisites:
• A supported Windows operating system running on physical hardware or as a Windows
guest on a supported hypervisor. For a list of supported operating systems, and CMS hardware
and software requirements and caveats, see HP Insight Management Support Matrix at the
following website:
http://www.hp.com/go/insightmanagement/docs
• Microsoft iSCSI Initiator, which you can download and install from http://www.microsoft.com
if it is not already available with the operating system on your application station.
• Insight Control server migration installed on an NTFS partition.
• Availability of ports 51124 and 51125 (or ports specified during Insight Control installation
for agent communications and HP Integrated Lights-Out (iLO) booting).
• Availability of port 51127.
• User account credentials with administrative rights.
• Free disk space of at least 300 MB per iLO boot, while booting a destination server for P2P
and V2P.
• The initial installation of Insight Control server migration can take 1 GB of storage space, and
each automatically booted destination server will need at least 300 MB of storage space on
the application station for non-Gen8 servers.
Verifying hardware and operating system support 17
4 Planning the migration
Planning a migration strategy
One challenge in migrating operating systems, applications, and data is modifying the migrated
operating system to boot on the destination server and to function properly on the hardware. Insight
Control server migration makes the required operating system changes for you.
To best prepare for a migration, consider developing a migration strategy before you run a
migration. Migration strategies vary depending on machine hardware, network landscape, and
applications. To develop a migration strategy, review the following before beginning your migration.
Preparing a schedule
Schedule preparation is an essential part of planning a migration strategy.
Be sure to include adequate time for copying data, because the source server will be offline until
the migration is complete. Large volumes take time to migrate. Under optimal conditions, 1 GB of
data requires 2 to 3 minutes to migrate. Using 2 minutes as a best-case scenario, migrating 500
GB of data might take more than 17 hours.
When a migration starts, the source server reboots to a minimal configuration so that no updates
occur on the source server during migration. Only those services required for the migration are
enabled.
Applications that normally run on the server are not available during migration. After the migration
is complete, the source server is restored to its premigration state.
Schedule the migration to occur at a time when the source server can be offline.
Considerations for multiboot systems
Although Insight Control server migration supports migrating multi-boot systems, consider the
following:
• A supported operating system must be set as the default operating system for the boot disk.
• The migration wizard enables the migration of all partitions with supported file systems.
Unsupported operating systems on those partitions are also enabled for migration, but Insight
Control server migration does not support them.
• If unsupported operating systems are migrated, they might be detected, but proper drivers
might not be installed. This issue can leave the unsupported operating system on the destination
server unable to be booted.
Migrating large NTFS partitions
Insight Control server migration cannot migrate NTFS partitions greater than 2 TB in size.
Resizing file systems for migration
During the migration progress, the partitions being migrated can be resized. There are some file
system caveats to be aware of that might affect the migration of your data.
Resizing Windows file systems
Insight Control server migration supports resizing and migration of NTFS volumes. However, some
conditions may prevent server migration from resizing NTFS partitions:
• Large NTFS partitions or NTFS partitions that have too many clusters, resulting in large volume
cluster bitmaps that cannot be resized. In some cases, the volume might be recognized as
18 Planning the migration
RAW (partitions in which no file systems exist). Although server migration can perform
migrations on these volumes, it cannot resize the volumes.
• Volumes that have bad clusters. Server migration does not support the migration of volumes
that have bad clusters. You must manually migrate volumes that have bad clusters to the
destination server after a migration.
If an NTFS volume is detected but cannot be resized, you must run a disk check (for example,
CHKDSK.exe) to verify that the volume has no bad clusters before you begin the migration process.
NOTE: Before installing SPP on the destination server, as part of postmigration task, ensure that
the server has a minimum of 1 GB of available disk space.
Resizing Linux file systems
Insight Control server migration supports file systems in LVMs, and it supports resizing and migration
of the following Linux journaling file systems:
• ext2
• ext3
• ext4
• ReiserFS
• LVMs
However, Insight Control server migration does not support Linux file systems that have bad blocks.
Make sure that the Linux source file system does not have bad blocks by running file system–specific
disk maintenance tools to examine the disk and mark bad blocks, like the file system consistency
check (fsck).
Manually disabling critical or hardware-dependent applications
Some hardware applications are bound to the source server and might need reconfiguration to
function as expected after a server migration.
For added safety, manually disable critical and hardware-dependent applications before you
migrate a source server. You can then manually re-enable these applications after the migration
is complete.
Manually disabling applications prevents them from starting on the destination server before they
are reconfigured for the destination server.
Examples of applications that must be disabled during migration include:
• Applications that rely on unique hardware serial numbers, BIOS or chassis IDs, NICs, MAC
addresses, or devices that authenticate a piece of software.
• Applications that store data on a volume different from that of the operating system. Insight
Control server migration retains drive letters (for example, F:) during migration, but hardware
differences between the source and destination servers can force the drive letters to change.
• Applications that depend on physical disk identifiers instead of drive letters. Depending on
the disk enumeration order for the destination server and selections made in the migration
wizard, the contents of a physical disk might have a different sequential identifier on the
destination server. In these cases, the application must be reconfigured to use the new physical
disk identifiers.
Manually disabling critical or hardware-dependent applications 19
5 Preparing software for migration
Verifying licenses for software to be migrated
Before you perform a migration, review all hardware, operating system, and application licenses
on the source server and acquire all valid licenses necessary for the destination server. Some
hardware, software, and OS license agreements might require you to purchase a new license for
the destination server.
IMPORTANT: Servers that have Windows OEM licenses are not supported for migration. For
licensing questions, contact HP support. For information about HP support, see “Support and other
resources” (page 73).
Migration security
Disabling firewalls
The source server Microsoft Windows firewall or Linux firewall and SELinux are disabled
automatically by server migration when a migration begins. The firewall and SELinux (if applicable)
are re-enabled after the migration is completed.
Before you perform the migration, you must manually disable, reconfigure, or remove other firewall
products. If you reconfigure a firewall product, you will be required to remove the product before
migration and reinstall it after migration.
If the firewall is not disabled or configured properly on the source server, application station, and
virtual machine hosts before a migration, the source server, application station, and virtual machine
hosts might not be able to communicate. Symptoms of this issue can include the following:
• The application station cannot detect the source server migration Agent for migrations.
• The source server hangs after booting into exclusive mode during migrations.
The following TCP ports are used for Insight Control server migration:
• Port 51124—For communication between the Insight Control server migration Web Service
and the Insight Control application service using Secure Sockets Layer (SSL)
• Port 51125—For communication between the Insight Control server migration Web Service
and iLO for autodestination boot
• Ports 51125 and 51126—For communication between the Insight Control server migration
Application Service and the migration agent on the source server
• Ports 51125 and 51126—For communication between the Insight Control server migration
Application Service and the migration agent on the destination server
• Port 51126—For communication between the migration agents on the source server and
destination server
• Port 51127—For use on the application station for Insight Control server migration Web
Service
• SSH port 22—For Linux migrations
20 Preparing software for migration
Figure 2 TCP ports in use during migration
NOTE: Insight Control uses the following encryption types:
• SSL RSA with RC4 128 MD5
• SSL RSA with RC4 128 SHA
• TLS RSA with AES 128 CBC SHA cipher suites. To enable the support of AES 256 and FIPS
140-2 cipher suites on server migration with strong cipher, use the utility: <Insight Control
server migration Installation Folder>/bin/cipherutil.cmd
Disabling antivirus software
For optimal performance during migration, verify that real-time scanning is temporarily disabled.
Also verify that no antivirus scans are running or are scheduled to run while the migration is
performed on the application station, source server, or virtual machine hosts.
Generating static or dynamic certificates
Static certificates are used when you run the server migration Source Agent manually on the source
server. However, dynamic certificates are generated and used when you use Insight Control server
migration to automatically deploy agents to the source and destination servers. HP recommends
that the agents be deployed automatically using Insight Control server migration.
Installing ProLiant Support Packs
PSPs contain sets of drivers to get a new ProLiant destination server running quickly after a migration.
Windows PSP executables can automatically be installed at the end of a Windows X2P migration.
• For Windows X2P migrations, upload the PSP you plan to use on the Upload Drivers tab of
the server migration UI. Also, Windows PSPs can be installed manually after migration.
• For Linux X2P migrations, you must manually apply the Linux PSP to the destination server after
the migration is complete.
Installing Service Pack for ProLiant
SPP contains sets of drivers and firmwares to get a new ProLiant Gen8 destination server running
quickly after a migration. SPP is installed automatically at the end of a Windows X2P migration.
• For Windows X2P migrations, upload the SPP you plan to use on the Upload Drivers tab of
the server migration UI. You can also manually install Windows SPP after server migration
Installing ProLiant Support Packs 21
NOTE: Before installing SPP on the destination server, ensure that the server has a minimum
disk space of 1 GB.
• For Linux X2P migrations, you must manually apply the Linux SPP to the destination server after
the migration is complete.
22 Preparing software for migration
Part III Migration
This part of the guide contains information related to steps 3 through 5 of the checklist provided in “Migration
checklist” (page 13), and methods for manually completing some the steps of the migration wizard.
Remember, this guide does not describe each of the steps in specific detail. You can find specific information
in the online help.
6 Preparing the source server and deploying the Source
Agent
Verifying Windows source server requirements
The physical or virtual Windows source server requires the following:
• Local system administrative credentials.
• A supported Windows operating system. For a list of operating systems, see HP Insight
Management Support Matrix at http://www.hp.com/go/insightmanagement/docs.
• Available disk space of at least 180 MB.
• The availability of ports 51125 and 51126.
• Screen resolution of at least 800 x 600.
• All detachable media removed.
• If the source server is an application station, disable the HP Insight Control server migration
Application Service and the HP Insight Control server migration Web Service.
Preparing a Microsoft Hyper-V source server
If you are planning to migrate a source server that has the Microsoft Hyper-V role enabled, perform
one of the following on the source server:
• Turn off the hypervisor by using bcdedit /set hypervisorlaunchtype off at a
command line.
After the migration, you can re-enable the hypervisor at a command line by using bcdedit
/set hypervisorlaunchtype auto.
• Remove the Microsoft Hyper-V role from the source server by using the server configuration
tools.
Verifying Linux source server requirements
The physical Linux source server requires the following:
• User account credentials with administrative rights.
• SELinux running in passive mode.
• A supported Linux operating system. For a list of operating systems, see HP Insight Management
Support Matrix at http://www.hp.com/go/insightmanagement/docs.
• Available disk space of at least 10 MB on /boot and 150 MB under the directory where the
Linux server migration Source Agent must be installed.
NOTE: When Linux Source Agent is launched remotely from the CMS, the default location
on the source server for agent installation is /root.
`
• The availability of ports 51125 and 51126.
• Verify that you have removed all unused boot entries from /boot/grub/menu.lst and the
corresponding initrd from /boot.
• Disable any scripts that might clean up the migration agent files on reboot or shutdown. For
instance, if the agent has been deployed manually to /root, make sure that no scripts will
clean up /root on restart or shutdown.
24 Preparing the source server and deploying the Source Agent
• To enable the display of the Linux source server agent in 64–bit RHEL, installation of the X.Org
X11 libXtst runtime library libXtst-1.0.99.2-3.el6.i686.rpm.
• The 32-bit version of glibc to run the Linux server migration Source Agent. The library is
present by default on 32-bit Linux installations, but you might need to install it manually on
64-bit Linux systems. The 32-bit version of glibc is available on your Linux OS installation
CD/DVD.
• For SAN Linux migration, destination server–specific Fibre Channel HBA firmware files installed
on the source server. These firmware files are available on the installation media of the Linux
OS. For example, if you plan to migrate to a destination server with SAN storage by using a
QLogic HBA, you must install qlogic-firmware-<version>.noarch.rpm on SLES OS
or ql2xxx-firmware-<version>.noarch.rpm on RHEL OS. For information on the
firmware files required and the installation instructions, see the respective HBA documentation.
• If an IPv6 DHCP server running on the network and if the source is a SLES OS running DHCP
client for IPv6, then the source may not boot in the safe migration mode. To resolve this issue,
you must disable IPv6 DHCP on all the NIC interfaces in the source server prior to migration
and restart the server manually after the migration.
Removing guest tools
Before you start a migration, you must remove guest tools if you are migrating a source virtual
machine. Guest tools are not applicable on the destination server and might cause issues with the
normal functioning of the network adapters, keyboard, and mouse. After the migration is completed,
you can reinstall the guest tools on the source virtual machine.
Choosing server migration Agents
Deploy and run migration Agents on the source server and the destination server before you start
a server migration.
Table 2 Server and migration Agent types
Virtual machine destination
1
HP ProLiant Gen8 servers must be booted automatically from the server migration wizard. When HP ProLiant Gen8
servers are used as destination servers, the manual boot option of the Insight Control server migration ProLiant Boot CD
is not supported.
The Source Agent does not run as a service on the source server, and you must apply the agent
for each migration. The agent will no longer run on the source after migration.
Deploying server migration Agents
Migration AgentServer
Windows server migration Source AgentPhysical Windows source server or source virtual machine
Linux server migration Source AgentPhysical Linux source server or source virtual machine
Insight Control server migration ProLiant Boot CD ISO filePhysical destination server
1
Insight Control server migration Virtual Machine Boot CD
ISO file
Deploying Agents
If you have administrative rights to connect to the source server, you can deploy a migration Agent.
NOTE: Shut down any running hypervisor or virtual machines on the source server before you
deploy the migration Agent. Failure to do so can result in improper IP address assignment and
can disrupt the migration.
Removing guest tools 25
Use one of the following methods. For additional information on these procedures, see the server
migration online help.
• HP Systems Insight Manager
Click Deploy→Deploy Drivers, Firmware and Agents→Install server migration Agent.◦
◦ By using the Quick Launch feature, select a source server, hover your mouse over the
Quick Launch link, and then select Install server migration agent.
• Server migration wizard
From the Deploy Agent tab of the migration wizard or from the migration wizard during
◦
migration setup for source servers
◦ From the Identify Source Server step of the migration wizard
NOTE: When the deployment is performed through Systems Insight Manager and the server
migration wizard, the agent launched from the CMS will not be valid after 7 days, and will
need to be stopped and re-deployed on source before the migration can occur.
• Manually running server migration Source Agent on the source server
Manually running server migration Source Agents on the source server
Deploying a Windows server migration Source Agent locally on the source server
1. Access the server migration Source Agent in the following folder on the application station:
<Insight Control server migration Installation
Folder>\Agents\SMP\cp009582.exe
Figure 3 Navigate to server migration Source Agent
2. Copy the cp009582.exe file to the source server, and then run the file. If a security warning
window appears, click Run.
3. To launch the server migration Source Agent, click Install.
26 Preparing the source server and deploying the Source Agent
Figure 4 Server migration agent install screen
When the server migration Source Agent is ready for migration, the following screen appears
on the source server.
Figure 5 Source Agent screen for Windows
Manually running server migration Source Agents on the source server 27
Loading...