Destination physical server prerequisites, San migrations in windows – HP Insight Control User Manual
Page 35
•
The GRUB Boot Loader is the primary boot loader on the source server.
•
Guest tools are uninstalled.
Destination physical server prerequisites
If migrating to a destination physical server, verify that the following prerequisites are complete:
•
The primary storage controller must be configured with drives attached.
•
The destination server must be booted to Insight Control server migration Boot CD ISO and
running migration agent.
Destination virtual machine host or virtual machine prerequisites
If migrating to a destination virtual machine, verify that the following prerequisites are complete:
•
Select one of the following:
Let Insight Control create the virtual machine automatically, and then boot it using the
Insight Control server migration Virtual Machine Boot CD ISO for virtual machines.
◦
◦
Create the virtual machine manually, and then boot the virtual machine manually using
the Insight Control server migration Virtual Machine Boot CD ISO.
•
Verify that the destination virtual machine host has sufficient system resources, including
processor, memory, and disk space to host the migrated virtual machine guest.
•
Temporarily disable any antivirus software auto-scans on the destination virtual machine host
to prevent interrupting the migration process. Re-enable the antivirus software after the
migration.
SAN migrations in Windows
IMPORTANT:
SAN migrations are not supported for Linux servers.
Insight Control supports Windows migrations to destination physical servers with Fibre Channel
SAN connectivity. To verify that your Fibre Channel HBA is supported, see the Insight Software
Support Matrix at the follow website:
The prerequisites for a migration to a server with Fibre Channel SAN connectivity are the same as
the prerequisites for migration to a destination physical server, described in
Windows server migration” (page 33)
and,
“Destination physical server prerequisites” (page 33)
with the following additional preparatory steps:
1.
Manually set up the SAN environment by doing the following on the destination server:
•
Create logical units on the storage
•
Configure SAN switches
•
Configure Host Bust Adapter (HBA)
2.
After setting up the SAN environment, boot the destination server using the Boot CD ISO.
3.
Run the migration wizard.
4.
Follow the relevant migration steps in
“Preparing for a Windows server migration” (page 33)
.
5.
In step 5 (Specify destination disks) of the migration wizard, verify that you have selected the
boot LUN that you configured in the HBA BIOS of the destination server when you migrate
the boot partition on the source server.
Prerequisites
35