Hp Insight Control User Manual download pdf (Page 38)

The prerequisites for a migration to a server that has Fibre Channel SAN connectivity are the same

as the prerequisites for migration to a destination physical server—described in “Preparing for a

Windows server migration” (page 35), “Preparing for a Linux server migration” (page 36),

and“Destination physical server prerequisites” (page 36)—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 HBA.

2. After setting up the SAN environment, boot the destination server by using the Boot CD ISO.

3. Run the migration wizard.

4. Follow the relevant migration steps in “Preparing for a Windows server migration” (page 35).

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.

NOTE: To migrate Windows 2003 to a SAN-connected destination server, you must first install

Service Pack 2 and the updated Storport storage driver (for more information, see http://

support.microsoft.com/kb/932755) on the source server.

You can perform a migration to a destination server with some source disks migrated to local disks

on the destination and some source disks migrated to SAN disks presented to the destination.

A local disk cannot be migrated to a SAN disk on the same server. That is, you cannot run a

DAS-to-SAN migration on the same server. For example, you cannot migrate a SAS disk on a

server to a SAN disk on the same server. The migration must be a migration from Server A to

Server B, where A and B are distinct servers.

Before you run an X2P migration to a SAN LUN, HP recommends that you disable any ports that

are not used for migrating to the destination HBA. Otherwise, if the operating system is migrated

to a SAN LUN connected to a Fibre Channel HBA in the destination server, the server migration

might not migrate to the primary LUN. Failing to disable unused ports might produce the error

message Error loading operating system when the destination server is booted.

Starting the migration wizard

After source and destination server agents are launched, you can start the migration from Systems

Insight Manager in two ways:

• Through the Deploy menu

• Through the Quick Launch feature

Launching server migration by using the Deploy menu

To launch Insight Control server migration from theDeploy menu, perform the following tasks:

1. In Systems Insight Manager, select the source server or source virtual machine. Make sure that

the source server is discovered properly and that the OS type and IP address are correctly

identified.

2. From the main wizard, select Deploy→Server Migration Tools, and then select the appropriate

migration option.

38 Migrating the servers

1 2 ... 33 34 35 36 37 38 39 40 41 42 43 ... 81 82

No comments

Hp Insight Control User Manual Page 38