Home > Blogs > VMware vSphere Blog


New NFS Best Practices Whitepaper available

A new NFS best practices white paper is now available. The paper looks at all aspects of using NFS in a vSphere environment. The paper was created with the assistance of our partners from EMC (Isilon), HDS & NetApp, and tries to find common agreement as to what are the best practices. It discusses networking configuration options, interoperability with other vSphere components and advanced settings. You can download the white paper from the VMware Technical Resources site here.

Get notification of these blogs postings and more VMware Storage information by following me on Twitter: @VMwareStorage

This entry was posted in Storage, vSphere on by .
Cormac Hogan

About Cormac Hogan

Cormac Hogan is a senior technical marketing architect within the Cloud Infrastructure Product Marketing group at VMware. He is responsible for storage in general, with a focus on core VMware vSphere storage technologies and virtual storage, including the VMware vSphere® Storage Appliance. He has been in VMware since 2005 and in technical marketing since 2011.

8 thoughts on “New NFS Best Practices Whitepaper available

  1. fletch00

    We appreciate the Netapp VSC plugin for vCenter tuning our VMware NFS datastore parameters according to best practice. Does this paper raise issues that are not addressed by VSC ?

    thanks

    Reply
    1. Cormac Hogan

      Obviously for NetApp, you should follow their guidelines. The parameters which are tuned by VSC are explained in the paper, and gives you a good idea as to why these settings are implemented.

      Reply
  2. Cormac Hogan

    Thanks Mike. We we going for a more generic approach with this paper, rather than calling out vendor specific configuration options. NetApp have their own BP paper for NFS, but if it doesn’t contain a .snapshot reference, I would reach out to them directly.

    Reply
  3. The Browser

    I would like to see more detailed reference architecture and examples based on LBT setup, static loading balancing/sharing using multiple subnets and NIOC. Following vendor best practise is always good, but I am big fan of KISS principle to achieve similar results.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>