Uhm, I see issues in this design, as NFS on windows is only mounted in "userland", not as a system device, so without any prior login activity with the same account running Veeam repository, the mount will not be available. I remember testing this options in the past and I dropped the idea to mount nfs on windows for this reason. There are other tools available on the market that can mount nfs as a proper disk under system, but at that point why not using SMB if the storage system exposing nfs can also expose smb? Or even better, from a performance standpoint, expose the volume with iscsi and remove a lot of abstraction layers?
EMEA Cloud Architect @ Veeam Software
Veeam VMCE #1