HP Virtual Connect Enterprise Manager Software - Manual (Page 12)

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 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 the 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 found 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 13)
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 with the Boot CD. For Gen8 servers, auto-boot option is only
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 in to the new server and configure the drivers, communication settings, and boot options.
12 Server migration concepts