Issue with synthentic full backups failingto NAS using NFS

[Robx]

Hi all,

we have started to have our clients synthetic full backups fail with the below error which is causing with retention not working as expected. Note incremental and fulls are working OK.

"Unable to apply retention policy: failed to delete backup files Error: Failed to call RPC function 'NfsIsExist': NFS4 status code: [88]. Cannot check exists of Backup_Job_-_Test. Error: A write fault occurred on the network. "

currently have a open ticket Case # 04634646

just hoping someone else has come across this before.

Thanks
Rob

[HannesK]

Hello,
and welcome to the forums.

Sounds like an infrastructure issue (permissions?). Speculating about the reason on a forum makes no sense. Please continue with support to get a precise answer.

Note: as you use NFS, I recommend to switch to active-full. As NFS has no block-cloning capabilities, the performance with merges is bad (block storage with XFS or REFS can do that much faster https://www.veeam.com/blog/advanced-ref ... suite.html)

Best regards,
Hannes

[soncscy]

Hey Robx,

>A write fault occurred on the network.

NFS isn't being funny here, you have a network situation or a permissions issue on the share.

Make sure the share access is anonymous:anonymous, or if you must use authentication, you must manually mount the share to some gateway server and specify that gateway in Veeam on the repository.

If that is not applicable, then put wireshark on the gateway you're using, start a dump and reproduce the issue.

But this is a stock network error message; check the wireshark data.

[Robx]

Thanks for the replies, strange thing was that this was working and then stopped working, no changes had been made to permissions or network. I will continue with the support ticket.

[roytan]

Hi there,

do you have any solution for the problem?

[PetrM]

Hi Roy,

Please contact our support team for detailed investigation of the issue, the error is quite generic and can happen due to different reasons. Most probably, it's related to network specific, thus Harvey's suggestion to collect and examine network traffic dump is still valid.

Thanks!