NFS4 status code: [0] ... failed with Hard I/O error

[JamesMcG]

Started implementing NFS share backups today. I'm doing so at two sites, first one went off without a hitch. Runs fast, just WORKS! I was so impressed.

Second site however, I've hit a snag. I'm not sure what's causing this error:
4/1/2020 10:16:34 AM :: Unable to backup nfs41://***.***.***.***:/export/project/share. NFS4 status code: [0]
During opening item /export/project/share nfs41_lookup() failed with Hard I/O error

The two sites are the same config. Versions of Veeam obviously are 10, and the storage is an intelliflash array from Tegile. Any suggestions?

[Dima P.]

Hello James,

Can you please raise a support case and share the case ID? Thank you!

[JamesMcG]

Sure, I was trying to cut you guys a break with all this working from home stuff. Figured I'd try the community first, but I'll create a ticket.

[JamesMcG]

Case ID#04097132

[JamesMcG]

It was the storage unit not serving NFS on the IP I had specified. I switched to a different IP and all is well.

As a side note, I'm so very happy to have this functionality. I spent way too many hours looking for a decent NFS/SMB solution. I tested a few half baked NDMP implementations. Dealt with so many vendors telling me to do a full replace of Veeam etc. I was able to hold my boss off by telling him to wait and see what Veeam does in v10. So glad I did, thanks for this!

[Dima P.]

James,

Glad you nailed it and thank you for your feedback. Let us know how the implementation goes and if need any further assistance. Cheers!

[JamesMcG]

I did run into an issue doing an offsite copy.

Failed to process NAS backup copy task Error: Agent: Failed to process method {MessageChannel.EstablishConnectionByRoles}: Failed to connect to the port [HQ-Backup.****.net:2507].

Any ideas? Other copies going to the same off site repo are fine.

[Gostev]

Check your firewall settings for the above port number.

[JamesMcG]

It was indeed the firewall. Since the destination repo is connecting back to the source server running the job it was blocked.