VMware

Storage VMotion and 10Gb Ethernet support for iSCSI SAN's | Main | Top Tips for Deploying VI

July 11, 2008

VMware is Storage Protocol Agnostic

Which storage protocol to choose?

The most common storage related questions we are being asked today are:

  • What is the best choice for running VI3 on shared storage?
  • Should we use Fibre Channel (FC), iSCSI or NFS?

The answer to these questions will depend on a number of variables and as such the same answer will not be the same for each environment. VMware currently supports deployment of VI3 on all three of those storage protocol choices, as well as on local ESX server storage, and is focused on enabling customers to be successful at leveraging the benefits each of those choices available for the virtualization environment. Although differences exist in which VMware features and functions are available on them, the current approach is to remove as many of those differences as possible so that customers can have more choices available to them.

There are many industry perceptions that exist when comparing FC to Ethernet based storage (iSCSI and NFS) and these generally apply to both the physical and virtual deployments. Even though virtualization does not resolve the differences which exist between these protocols, VMware is focused on providing as level playing field as possible when it comes to using the different storage protocols.

What is supported?

Today some VMware features, functions and products are available on FC but are not an option when using NFS or iSCSI.

Summary of current feature support across protocols:

Type

Boot VM

Boot ESX Server

VMotion

HA/DRS

RDM

MSCS Cluster

VCB

SRM

SVM

Lab

Mgr

Stage

Mgr

Life

Cycle

Mgr

Fibre Channel

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

iSCSI

Yes

Yes*

Yes

Yes

No

Yes

Yes

Yes

Yes

Yes

Yes

NAS

Yes

No

Yes

No

No

Yes

No

Not

Yet

Yes

Yes

Yes

Local Storage

Yes

Yes

No

Yes

No

No

No

Not

Yet

Yes

Yes

Yes

*  Boot from hardware iSCSI only (not supported from software iSCSI)

VMware is working to removing as many of those differences as possible so that the selection criterion for choosing a storage protocol is based on the differences that apply to both the physical and virtual world instead of what VMware features and products are available on one protocol but not another.

VMware will also address these differences in an order determined by the proportion of our customer deployments on each storage protocols. We have a great deal of work to do to complete this vision. But that is were we are headed.

Are there performance differences?

Performance is one of many considerations when choosing a storage protocol for the virtualization environment. However performance in a VI3 deployment is a multi­dimensional measurement that varies based on many factors. The number of ESX serves in the VMware cluster, number of VMs sharing a common pool of storage, block size, random vs. sequential ratio and read vs. write ratio. Today most benchmarks and comparisons tend to measure only one dimension and do not represent a typical multi ESX server infrastructure with multiple VMs running on them. The performance difference found in the physical world when comparing protocols is consistent with what is found in the world of virtualization. A VMware paper which provides some more details on storage protocol performance comparison is posted on our website. This paper shows that all network storage connection options available to ESX Server are all capable of reaching a level of performance limited only by the media and storage devices. When compared in terms of CPU costs, Fibre Channel and hardware iSCSI are the most CPU efficient because they offload the processing to the HBA, but in cases in which CPU consumption is not a concern, software iSCSI and NFS can also be part of a high performance solution.

Conclusions

One needs to consider not which protocol is the best choice for deployment of virtualization, but instead which virtualization solution provides the best support for multiple protocols? VMware not only supports the use of many storage protocol choices, but also provides a means to move VMs from a datastore on one protocol to a datastore on a different protocol while the VM remains up and running. Storage VMotion provides the means by which if one selects one protocol for a VI3 deployment, we enable switching to another protocol with much less disruption than any other virtualization solution offering available today.

While Storage VMotion is fully supported with FC today, we are headed in the direction of having it supported across all VI3 storage connectivity options (FC, iSCSI, NAS and local storage) so customers can seamlessly move from one type of storage to another.

So to close out on the question of which protocol is the best choice, the answer is all of them that VMware VI3 supports. And if you change your mind, or the choice first made was not the right one, VMware is providing the ability for one to move virtual machines to another storage protocol without huge hassle. In short, Vmware is all about being storage protocol agnostic.

If there is something you think I need to cover, let me know, please email me at: pmanning@vmware.com

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341c328153ef00e55396df048833

Listed below are links to weblogs that reference VMware is Storage Protocol Agnostic:

Comments

When will SVM be supported on NFS?

SVM support for NFS is currently being tested by VMware QA and yet there is no specific date committed at this time for when that work will be completed.
We are not aware of any issues as to why it might not work, but until the testing is done, we can not commit to a date or release vehicle by which it will be supported. Expecting 3.5 U3 or ESX 4 as likely options at this point.

Hello
I'm new to VMware and I work for Demand Technology Software (please see URL in the entry form). We are starting the process to join the TAP program. Our customers using VMware have been asking for host performance data integrated with guest data through the standard Windows methodology. I'm getting that development started. I've downloaded the SDK, read all of the documentation on Performance Counters I could find, and just got ESXi 3.5 running on a test server.

We got a report from someone who was at VMWorld to the effect that "ESX 4 will not have APIs to talk to ESX and that the data will only be available through Virtual Center..." In our context, that would mean performance data via QueryPerf(...) would not be supported.

I've searched technical papers and the communities for ESX 4 information and this blog was the only resource that returned a hit. I think this person is misinterpreting something he heard, but we need to check this out.

We have not signed an NDA since we are just getting rolling on this (be happy to if required), and we don't need anything more specific about ESX 4. We just want to know whether the APIs will support querying for performance groups and counters in the same manner as in ESX 3.5.

Thanks in advance for your time.

Stets Newcomb
MailTo: stets.newcomb@mesanetworks.net
(303) 775 3589

Post a comment

If you have a TypeKey or TypePad account, please Sign In


Categories