User guide

Technical white paper | HP Enterprise Virtual Array Storage and VMware vSphere 4.x and 5.x configuration best practices
36
Figure 20. RDM datastore
Comparing supported features
Table 6 compares features supported by VMFS and RDM datastores.
Table 6. Datastore supported features
Feature
VMFS
RDM
VMware Native Multi-pathing (NMP)
Yes
Yes
VMware vMotion
Yes
Yes
VMware Storage vMotion
Yes
Yes
VMware FT
Yes
Yes
VMware sDRS
Yes
No
VMware SIOC
Yes
No
MSCS
Yes
11
Yes
Implementing a naming convention
When working with multiple datastores, VMDKs, and RDMs in conjunction with large clusters or SANs, management can
become complex. Unless you use a suitable naming convention, it may be very difficult to locate a particular datastore for
management or troubleshooting purposes.
For example, array model names should not be included in the naming convention – if you move a Vdisk from one EVA
model (such as the EVA8100) to another (such as the EVA4400), the naming convention would break down. You should not
include the Vdisk number in a datastore or RDM naming convention because the number for a Vdisk in Datacenter A may not
be maintained when the Vdisk is replicated and presented to a host in Datacenter B. Similarly, you should not include Vdisk
size in a naming convention because it is probable that this size will change.
To avoid confusion, you need detailed documentation on each array, datastore, Worldwide Name (WWN), and host name. In
addition, avoid using the following in the name for a datastore or RDM:
• EVA model or controller name
• EVA WWN (or any part thereof)
• Vdisk number
11
Only supported with vRDM using VMs in a cluster within a box configuration.