Creativa - Fotolia
One storage issue that occasionally proves to be problematic is vSphere 6 support for NFS 4.1. Previously, vSphere supported only NFS version 3. While support for a newer version of NFS is not a problem in and of itself, issues can occur if you use multiple NFS versions.
When you create a new datastore, the New Datastore wizard asks if you want to use NFS 3 or NFS 4.1. However, the NFS version screen also displays the following warning message: "Use only one NFS version to access a given datastore. Consequences of mounting one or more hosts to the same datastore using different versions can cause data corruption."
There are also some vSphere features -- such as Storage DRS, Storage I/O Control, Site Recovery Manager and Virtual Volumes -- that cannot be used with NFS 4.1. Legacy fault-tolerance mechanisms cannot be used with NFS 4.1 either, but the newer fault-tolerant mechanisms available with the vSphere 6 release do work with NFS 4.1.
Security is another issue that must be addressed when making the transition to NFS 4.1. Although NFS 4.1 still supports the AUTH_SYS mechanism, Kerberos is preferred because it is far more secure. If you create a new datastore that uses NFS 4.1, the New Datastore wizard will give you the option to use Kerberos-based authentication. If you choose Kerberos, there are two situations you need to be aware of:
VSphere 6 doesn't surpass expectations
Hana and Hadoop get a boost with release of vSphere 6
Quiz: Updates and features in vSphere 6
Dig Deeper on Storage for virtual environments
Related Q&A from Brien Posey
The backup-as-a-service platform is a popular use of cloud-based infrastructure. With new products and features launching, it's important to plan out... Continue Reading
IT pros must understand that their desktops' upgrade method, workload and other factors affect whether the Windows 10 system requirements are ... Continue Reading
With container storage a major trend, it's important to ensure data protection. These five guidelines will help you properly back up Docker ... Continue Reading