
NFS Datastores
Learner Objectives
After completing this lesson, you should be able to meet the following objectives:
- Identify NFS components
- Recognize the differences between NFS 3 and NFS 4.1
- Configure and manage NFS datastores
NFS Components
An NFS file system is on a NAS device that is called the NFS server.
NFS v3 and NFS v4.1
An NFS datastore can be created as either NFS 3 or NFS 4.1.
NFS 3 | NFS 4.1 |
ESXi managed multipathing | Native multipathing and session trunking |
AUTH_SYS (root) authentication | Optional Kerberos authentication |
VMware proprietary client-side file locking | Server-side file locking |
Client-side error tracking | Server-side error tracking |
NFS Version Compatibility with Other vSphere Technologies
vSphere supports NFS 4.1 to overcome many limitations when using NFS 3. Both NFS 3 and NFS 4.1 shares can be used, but you must consider important constraints when designing a vSphere environment in which both versions are used.
vSphere Technology | NFS 3 | NFS 4.1 |
---|---|---|
vSphere vMotion and vSphere Storage vMotion | Yes | Yes |
vSphere HA and vSphere Fault Tolerance | Yes | Yes |
vSphere DRS and vSphere DPM | Yes | Yes |
Stateless ESXi and Host Profiles | Yes | Yes |
vSphere Storage DRS and Storage I/O Control | Yes | No |
Site Recovery Manager | Yes | No |
vSphere Virtual Volumes and vSphere Replication | Yes | Yes |
vRealize Operations Manager | Yes | Yes |
Host Profiles | Yes | Yes |
Configuring NFS Datastores
To configure an NFS datastore:
- Create a VMkernel port:
- For better performance and security, separate your NFS network from the iSCSI network.
- Create the NFS datastore by providing the following information:
- NFS version: 3 or 4.1
- Datastore name
- NFS server names or IP addresses
- Folder on the NFS server, for example, /templates or /nfs_share
- Hosts that mount the datastore
- Whether to mount the NFS file system as read only
- Authentication parameters
Configuring ESXi Host Authentication and NFS Kerberos Credentials
As a requirement of Kerberos authentication, you must add each ESXi host to the Active Directory domain. Then you configure NFS Kerberos credentials.
Configuring the NFS Datastore to Use Kerberos
When creating each NFS datastore, you enable Kerberos authentication by selecting one of the security modes:
- Kerberos5 authentication
- Kerberos5i authentication and data integrity
Unmounting an NFS Datastore
- Unmounting an NFS datastore causes the files on the datastore to become inaccessible to the ESXi host.
- Before unmounting an NFS datastore, you must stop all VMs whose disks reside on the datastore.
Multipathing and NFS Storage
For a highly available NAS architecture, configure NFS multipathing to avoid single points of failure.
Example of a multipathing configuration:
- Configure one VMkernel port.
- Attach NICs to the same physical switch to configure NIC teaming.
- Configure the NFS server with multiple IP addresses (same subnet is OK).
- To better use multiple links, configure NIC teams with the IP hash load-balancing policy.
Enabling Multipathing for NFS 4.1
- NFS 4.1 supports native multipathing and session trunking.
- To enable multipathing, enter multiple server IP addresses when configuring the datastore.
Review of Learner Objectives
After completing this NFS Datastores lesson, you should be able to meet the following objectives: • Identify NFS components
- Recognize the differences between NFS 3 and NFS 4.1
- Configure and manage NFS datastores