Hi ​@Marcel.K,

Can you share some more details about your environment? Which components of Veeam do you use (simple deployment or advanced deployment, so everything on a single server or split)?

Which OS are the components running on? Are all components within the same network?

How did you check the network? Basically you should disable IPS / IDS on the firewall (in case there is one) for that traffic in any case because this can lead to partial packet / connection latency or loss.

You also could / should check the OS firewalls of the components.

Also I recommend opening a Veeam support case to let the support team check logs (which you can post here as well if you want).

Hope that gives a first idea. Best

Lukas

Do you use a specific gateway server for the NFS repository or automatic?  Try specifying one and see if that helps.

Hi ​@Marcel.K -

Seems someone had a communication issue with NFS a little while ago (tho different error) and some suggestions were given there:
 

Have you looked at logs (C:\ProgramData\Veeam\Backup\<job-name>) to see if there is more detailed info on what the timeout could be?

I also see a Forums post where, tho NFS (and SMB) are supported for targets, they aren’t really recommended:
https://forums.veeam.com/veeam-backup-replication-f2/nfsv4-as-a-repository-t82053.html

I would look at the Gateway server as Chris suggests to start, again..as long as you’re sure there are no network issues (blocked or used needed Veeam ports, OS firewall or UAC, A/V issues exclusions). And if that looks good, you may need to open a ticket as Lukas suggests.

Best.

we are using specific redhat VMs as gateways as hana is producing high load

communication between VBR and gateway is over vlan1

communication between gateway and repository is over vlan2 (without gw)

hana is communicating over vlan3

so VBR and gateway have all 3 networks

we do not have IPS/IDS on firewall, even local firewall was off

i have opened several support cases, but they pointed into nfs protocol

so that’s my question if someone has any experience with tunning of nfs 4.1 protocol?

Ah, ok. Well, using Linux removes some of my suggestions to look at  I don’t use NFS myself so have no further suggestions personally Marcel. 

Are you able to switch to NFS3 and check the performance?  I would suggest using the vendor page to check for articles on best practices, etc. or Google.  Every vendor and NAS is different for tuning, etc.

Hello  Chris.Childerhose, coolsport00, lukas.k, Anandu,

thank you very much. I appreciate so much of your comments.

I did extension of one value in nfs.conf

threads=1024

It helped something, but looks for more tunning ...

Yes, nfs repository is not recommended, but this was an announcement much later - i had nfs repository already 5 years.

We use it for plugin backup and is really not good, if there are more plugins than 20 customer VMs.

In the background i had good discussion with Veeam. There is some enhancement in Veeam13 regarding NFS repository, but we agreed, that we need some feature from Veeam to adapt on our design.

Thanks for the update ​@Marcel.K . Interested to see what Veeam is coming out with for NFS in v13.

Best!

It definitely will be interesting to see what v13 brings and hopefully will help to solve your issue.