This will result in faster backups and an even smaller load on production workloads. With the complete visibility of single files allowed by the NFS share, NFS users will be able to backup and replicate VMs directly from the NAS array and avoid the need to cross the hypervisor layer for their activities.

With it, any new Veeam proxy will run our new and improved NFS client to directly access any NFS share exposed to VMware vSphere, supporting both the traditional NFS v3 and the new NFS 4.1 available in vSphere 6. Internally, we call this feature Direct NFS. Now, in v9, something similar to Direct SAN processing mode will finally be available for NFS as well.

All of the NFS-specific issues VMware backup has had in the past years didn’t help, either. For a long time, NFS users have felt a bit like second-class citizens in the virtualization world, and the lack of direct access to an NFS storage in VDDK to read data during backup operations was surely one reason to “envy” block storage users. The first new feature we are announcing today is something I waited a long time for personally, and I suspected it was about to come when we had our first NFS client in v8 (as a part of our NetApp integration). We already announced a new addition in our list of supported storage arrays for our storage snapshots integration (EMC VNX/VNXe), but this isn’t the only storage news-on the contrary, there are plenty of them, and I’ll cover some of them in this post. The upcoming Veeam Availability Suite v9 has tons of enhancements and new features, but improvements around primary and backup storage will surely be one of the biggest parts of our next release.

Nfs 2015 free trail