
consistent data-disk replica of the RDM volume to a virtual machine connected directly (via
iSCSI) to a CLARiiON storage system or a physical server. If the application data disk replica
needs to be assigned to the VMware ESX server, the LUN must be manually placed in the
VMware ESX server storage group, and the VMware administrator must then assign the replica
(application data disk) to an existing virtual machine.
For more information on using Replication Manager with VMware and CLARiiON storage systems, refer
to the EMC Replication Manager Administrator’s Guide available on Powerlink.
CLARiiON and VMotion
Migration with VMotion allows you to move a virtual machine between two ESX servers while the virtual
machine is powered on and performing transactions. When a migration with VMotion is performed, the
operations of the virtual machine can continue uninterrupted. The virtual machine must reside on a SAN
LUN accessible to both source and destination hosts. VMotion only moves the virtual machine
configuration file and memory contents to the alternate host. Any disks assigned to the VM are moved by
transferring their ownership.
The conditions for VMotion to work are:
• The VMware vCenter server and client must be installed on a Windows system.
• A Gigabit Ethernet connection is required between the two ESX Server hosts participating in VMotion
migration.
• The guest operating system must boot from a CLARiiON LUN. The virtual machine boot LUN and its
associated data disks must be shared between the source and destination hosts.
• VMware VMotion is supported with Fibre Channel and iSCSI connectivity to CLARiiON storage
systems. Furthermore, VMware VMotion is supported in a configuration where both of the following
occur:
• A single LUN is presented to two VMware ESX Server nodes.
• The ESX Server nodes are in a cluster in which one node accesses the LUN via FC and the other
node accesses the LUN via iSCSI.
CLARiiON storage systems preserve the LUN HLU number across both protocols. Therefore, when a
LUN is presented via FC to one host and iSCSI to another, a false snapshot is not detected.
• VMFS and RDM volumes are supported with VMotion.
• Both hosts must have identical CPUs (both CPUs are P4, for instance) unless VMware’s Enhanced
VMotion Compatibility mode is used. The CPUs must also be manufactured by the same vendor.
Migration with VMotion cannot occur when virtual machines are in a raw, clustered, or nonpersistent
mode.
Figure 20 shows two ESX servers with three NICs each. The recommended number of NICs is three;
two is the minimum requirement. A crossover or gigabit LAN connection should exist between the two
gigabit NICs on the two VMware ESX servers. For ESX 2.x, a virtual switch must be created with the same
network label on both servers for the two network cards to communicate. In VMware ESX 3.x/ESXi, a
VMotion VMkernel port group on a vSwitch must be created on both ESX servers for VMotion migration.
VMotion with VMFS volumes
In order to perform VMotion with VMFS volumes, the following prerequisites must be met:
• All VMFS volumes assigned to the virtual machine that is to be migrated must be shared by both ESX
servers.
• VMFS volumes must be in public access mode.
VMware ESX Server identifies VMFS-2 volumes by their label information. For VMFS-3 volumes, they
are identified by the Host LUN number. Hence, as a best practice (unless doing boot from SAN for the
EMC CLARiiON Integration with
VMware ESX Server
Applied Technology 34
Comentarios a estos manuales