Feature Request: Include health checks in throttling

[SimonB-GMA]

Hi,

Please close this if I am not correct in my assumptions.

Based on an issue we experienced today, it appears that health checks do not take notice of any network throttling limits that are set.

This is mentioned briefly in this post from 2018. veeam-backup-replication-f2/network-thr ... 48808.html

If they do ignore network throttling, the please can that be changed? either by including them in the general throttling mechanism or by setting a throttling schedule specifically for health checks.

Thanks
Simon

[HannesK]

Hello,
just to be sure... are we talking about iSCSI? Then traffic rules cannot apply because iSCSI is like a "local disk" and there is not "network traffic" to a "local disk"

Best regards
Hannes

[SimonB-GMA]

Nope.

We have the following.

• A server holding a repo in the UK called UKREPO-01.

• A server holding a repo in the US called USREPO-01.

• A VBR instance running as a VM on UKREPO-01 called VBR-01.

• The two sites are connected via VPN.

• The repo's are configured in VBR as direct attached storage using the Windows server agent (for want of a better name)

The health check was running from the VBR box in the UK on data held in the REPO box in the US.

The traffic being generated was saturating the inter-site link and did not appear to respect the bandwidth limits set in VBR on the VBR box.

[HannesK]

Hello,
that sounds wrong. Health checks run locally on the repository server. If it's not iSCSI or SMB, then support should check whether it's really health checks and find the root cause for the traffic.

Please post the case number for reference.

Best regards,
Hannes