Hi guys,
I have tried multiple times, never works, if you go back and select CIFS instead works, so this is an issue that should be addressed on the ISO Try it on your side
Best regards
Jorge de la Cruz
Senior Product Manager | Veeam ONE @ Veeam Software
I got the same error only once, although after I performed a VM reset NFS mounts worked fine on the very same VM and iso. Played around with VM settings but never managed to catch the error again.
Could you please share the VM settings (hardware version, network settings etc) as well as the info about your Hypervisor?
I have the same error.
Rebooted the VM several times, tried to manually configure via command line but I always get same error: rpc.statd is not running.
I got the same error when I was trying to connect to CentOS 7.2 NFS share. However when I tried to connect to another NFS (RHEL 7.2) NFS share everything worked fine for the same VM and .iso. Could you double check if the error persists for different NFS servers please?
I'm having a similar issue restoring from an Openmediavault NFS share. I tried restoring to a VM in ovirt 4.1.0 and then in VMware ESXI 6.0.0. I tried mounting the share in command line with:
mount.nfs -o nolock SERVER_IP:/export/share /mnt/veeam
and it comes back with Protocol not supported.
If I run it without -o nolock,
it comes mount(2): No such file or directory.
The VM is a CentOS 7.2 VM and backups run just fine.
I'm having a similar issue restoring from an Openmediavault NFS share. I tried restoring to a VM in ovirt 4.1.0 and then in VMware ESXI 6.0.0. I tried mounting the share in command line with:
Could you please try to connect to some other NFS share from recovery media to see of the error occurs?