HP Insight Control 7.3 Update 1 Getting Started Guide

10 Migrating existing physical or virtual servers to another
server
Insight Control server migration makes it easy for you to upgrade or replace your existing server
or to implement virtualization. Server migration features enable you to replicate servers that are
running correctly, but that might be under-performing or that are over-provisioned, to a new physical
or virtual server.
The server migration application enables you to perform Physical-to-ProLiant (P2P), Virtual-to-ProLiant
(V2P), Physical-to-Virtual (P2V), or Virtual-to-Virtual (V2V) migrations from a single integrated
graphical user interface.
Migrations are supported from any server (regardless of hardware vendor, 32 bit or 64 bit) to the
latest HP ProLiant or BladeSystem server technologies.
Launching the server migration application
Table 8 Launching the server migration application
DescriptionFrom the CMS console management GUI
Provides the following possible options, depending on the type of servers
discovered:
Deploy→server migration Tools
• Physical to ProLiant (P2P)... migrates a physical machine to an HP
ProLiant server.
• Physical to Virtual (P2V)... migrates a physical machine to a virtual
machine guest within a virtual machine host.
• Virtual to ProLiant (V2P)... migrates a virtual machine guest within a
virtual machine host to an HP ProLiant server.
• Virtual to Virtual (V2V)... migrates a virtual machine guest between
virtualization layers.
Basic server migration procedure
To perform server migration, follow these steps.
1. Launch the server migration application wizard.
2. Deploy the server migration Source Agent onto the appropriate source server, which can be
either physical or virtual.
NOTE: Deploying the server migration tool launches a wizard that guides you through these
migration steps. For more information, see the HP Insight Control server migration User Guide.
3. Select the disk volumes of source server which needs to be migrated and complete step 2 of
migration.
4. Create the necessary disks on the destination server(s) using the appropriate disk configuration
tool.
24 Migrating existing physical or virtual servers to another server