Restore failed - unable mount NFS share

[Jango76]

I try to restore backup of real PC to virtual PC. Backup created with Veeam v.1.0.0.678.BETA2, saved on NFS share. When I booted virtual PC from Veeam recovery media, to restore volume backup, get next error:


If I switch to shell, NFS mount still not working, but when I reboot to installed in virtual machine OS (Debian 8 x64, same as real PC), NFS share mounts without errors.

[PTide]

Hi,

Which command did you use in shell? Was it mount -t nfs or mount.nfs4? Also is the shared folder already mounted in some other system? If so then could you try to unmount it please and try mounting it from Recovery Media again? What's the NFS server that you use, what distro is inside and what is the version of NFS that is used to export?

Thanks

[Jango76]

Shared folder doesn`t mounted in other system, we using QNAP NAS TS-469 Pro as NFS server.

[nielsengelen]

Mounting it is case sensitive. Is the folder you shared called "Public"?

[PTide]

Also I'm curious if there is a direct connection to NAS or there is a switch inbetween? Please try to run mount from the command line using the verbose mode:

Code: Select all

mount 192.168.10.50:/Public /media/nfs -v

and post the output.

Thank you.

[Jango76]

Mounting it is case sensitive. Is the folder you shared called "Public"?

[Jango76]

Also I'm curious if there is a direct connection to NAS or there is a switch inbetween? Please try to run mount from the command line using the verbose mode:

Code: Select all

mount 192.168.10.50:/Public /media/nfs -v

and post the output.

Thank you.

And mount in booted installed in VM OS Debian 8:

[PTide]

Ok, it seems that your QNAP does not support NFS v4 and recovery media NFS client does not even try to connect using v3 for some reason. Please try to force v3 usage:

Code: Select all

mount 192.168.10.50:/Public /media/nfs -v

Also please tell me what firmware version does your QNAP have?

Thank you

[Jango76]

Ok, it seems that your QNAP does not support NFS v4 and recovery media NFS client does not even try to connect using v3 for some reason. Please try to force v3 usage:

Code: Select all

mount 192.168.10.50:/Public /media/nfs -v

Also please tell me what firmware version does your QNAP have?

Thank you

Firmware is QTS v4.2.2

[PTide]

I'm sorry, it's my bad - the command supposed to be

Code: Select all

mount -o vers=4 192.168.10.50:/Public /media/nfs -v

Anyway we've already confirmed that recovery media does not work well with NFSv3. If you want to test the recovery procedure then please either place the backup onto usb drive or use some other type of a shared folder (CIFS or NFSv4).

Thank you.

[mwburn]

When I boot from the iso, I'm unable to mount the shared folder. The connection attempt fails with an error that "-o nolock" needs to be used (or rpc.statd needs to be started).

I can go into command line mode and try mounting manually using the -o option (plus several options), but haven't had any success. If I explicitly set the nfs version to 4, I get an invalid protocol error.

The shared folder we're trying to mount is on an EMC Isilon system.

[mwburn]

When I boot from the iso, I'm unable to mount the shared folder. The connection attempt fails with an error that "-o nolock" needs to be used (or rpc.statd needs to be started).

I can go into command line mode and try mounting manually using the -o option (plus several options), but haven't had any success. If I explicitly set the nfs version to 4, I get an invalid protocol error.

The shared folder we're trying to mount is on an EMC Isilon system.

So since this got merged into this thread, and I've already tried everything here, does that mean there's no solution?

[nielsengelen]

Can you manually mount it without any issues on another server?

[mwburn]

Can you manually mount it without any issues on another server?

Yes. I can mount the same shared folder on CentOS.

When I go into command line mode and try and mount (using -o nolock,vers=4), I get a "Protocol not supported" error.

[PTide]

This is a known bug and is already fixed for GA. Possible workarounds has been already mentioned in my previous post, and there is no way to fix it in the current recovery iso without rebuilding the iso.

Thank you

[mwburn]

This is a known bug and is already fixed for GA. Possible workarounds has been already mentioned in my previous post, and there is no way to fix it in current recovery iso without rebuilding the iso.

Thank you

Bummer, since that possible workaround didn't work.

[PTide]

Do you mean that you've tried to connect to NFSv4 share and it did not work either? If so then what is the version of NFS your Isilon is running?

Thanks

[mwburn]

Do you mean that you've tried to connect to NFSv4 share and it did not work either? If so then what is the version of NFS your Isilon is running?

Thanks

The Isilon wasn't configured for V4. Once it was changed, it can now be mounted.

[Jango76]

Anyway we've already confirmed that recovery media does not work well with NFSv3. If you want to test the recovery procedure then please either place the backup onto usb drive or use some other type of a shared folder (CIFS or NFSv4).

Thank you.

Release version of recovery media (1.0.0.944) now worked with NFSv3 - I tested backup&restore PC FS volumes with the same QNAP NAS.

[PTide]

Good to hear that! Thanks for your feedback!