@fgallego
Actually no, When you mount a given NFS share onto the VMDR appliance, it is perceived as a LOCAL storage device.
VMDR should see/treat it as if it were a drive installed inside that machine.
Mind you this procedure was created and tested on VMDR, so if you're using the new VDR I expect it will not work.
As far as things that could have gone wrong, I shall for the nonce assume you did not paste the fstab line as it is,
(You need to edit it to reflect the needs of your network)
Also important is that the NFS share you created be EMPTY when you initially set it up.
I know that these responses may not be that helpful, but we ARE limited in terms of the lack of good error reporting in VMDR.
I mean 'Problem with destination' Wow, that's useful. Thanks, I would have never guessed that it had a problem because it failed 
Without more info it's quite difficult to diagnose, and all I can do for you is venture some guesses.
Did you see anything more informative in the console error display?
You can get more useful information from using the dmesg command in the console, and by 'moreing' the log files, which reside nominally in /var/log/nfsd
(You MAY need to increase logging verbosity on NFS, which you should be able to do in /etc/nfs/nfslog.conf)
Were any errors spawned when installing NFS to the VMDR appliance?
Can you tell us what kind of device your NFS share resides on? (I.E. NAS appliance, Linux Box, Windows Box, you did not say...)
The fstab entry may vary WILDLY in terms of the 'share a address' between some products....
For instance, if you are using a QNAP NAS device it would be something like: [IP of QNAP]:/share/[name of share you created] instead of the syntax outlined above
And no, this 'workaround' while having always worked awesomely for me, is NOT what vmware would call
a 'supported solution', but I will help if I can