6Step 6. Migrate Virtual Machines and Virtual PortsMicrosoft VMM2008 allows you to quickly migrate VMs from one host to another. Depending on the medium of transferof the VM files, there can be either LAN- or SAN-based migration of VMs. This section defines the requirements for SANtransfers, describes how to start a SAN transfer, and discusses how NPIV plays a role in SAN transfers.Requirements for a SAN Transfer❑ Both the source and destination hosts involved in a transfer of a VM need to have physical access to thestorage array presenting the LUNs.❑ Both the source and destination hosts must have NPIV-capable adapters connected to an NPIV-capable switch.❑ The VM and all its associated files (VHDs) must reside on the SAN as seen through an NPIV virtual adapterport (not on a local disk).❑ The LUN must be configured as a basic/fixed disk and a single volume must be created on the basic disk.❑ A single VM and all its associated files must be placed on this volume.❑ Both the source and destination volumes must be formatted with the NTFS file system.❑ There must be one-to-one mapping of a LUN to a VM.Performing SAN TransfersMicrosoft VMM2008 can intelligently identify and report if all requirements of a SAN transfer have been met. Performthe following steps to determine if all the requirements of a SAN transfer have been met, and to start SAN transfer.1. In VMM, click the Actions tab. Under Virtual Machines, click Migrate.2. The Migrate Virtual Machine Wizard dialog box displays. Choose the destination host for the VMmigration.3. When all the requirements of SAN transfer have been met for the selected destination host, the screendisplays “This host is available for SAN migrations” in the SAN Explanation tab.4. Click Next. Select an NTFS formatted and migration capable volume available on the destination host.5. Click Next to complete the Migrate Virtual Wizard and start the migration process.6. Monitor the migration status through the Jobs windows by clicking the Jobs tab in the left pane ofVMM.7. Verify that the virtual HBA port associated with the Virtual Machine has been migrated to the destinationhost. The entry for the virtual HBA port in the FC switch Name Server has moved from the physicalport of the source server to the physical port of the destination server.8. You do not need to re-configure the switch zoning and the selective LUN presentation/LUN maskingon the storage array. The migration of the virtual HBA port (WWPN), along with the Virtual Machines,enables quick and easy Virtual Machine migration.