- This topic has 3 replies, 2 voices, and was last updated March 12, 2020 by Contara T.
Bandwidth Regulator Consequences
Network OMarch 11, 2020 03:58:35 PM
This question relates to KB 000002271: a bug in the bandwidth regulator within all versions of 6.5 that can have disastrous effects on traffic to target sites.
We still have some customers on version 6.5, something we expect to remedy within the next month, however in the meantime this problem periodically manifests itself with some of them. We are aware of the workaround that involves disabling the bandwidth regulator at the source sites but what is not clear is whether this disable all throttling completely. A couple of our customers have bandwidth that they share with other traffic in their organization apart from Zerto and the time-based throttle ensures that Zerto will not impact other services during business hours.
We would like to confirm if disabling this will also disable the time-based and/or IO-based throttles.Contara TMarch 11, 2020 07:52:55 PM
My name is Contara from Zerto support.
Regarding your question:
We would like to confirm if disabling this will also disable the time-based and/or IO-based throttles.
When disabled “Bandwidth Throttling – Limit” it shouldn’t be affecting the time-based and/or IO-based throttles.
Thanks.Network OMarch 11, 2020 09:01:40 PM
Thank you for your response but I am unclear about your answer. We are referring to the section Site Settings -> Performance & Throttling -> Advanced -> “Enable Bandwidth Regulation”. Per the mentioned article, the only way to get around the problem in 6.5 until an upgrade to 7.0 can be done is to un-check the box next to “Enable Bandwidth Regulation”. The question was meant to ask, “if we un-check that box, will time-based and/or IO-based throttling also turn off?”
Thank you.Contara TMarch 12, 2020 01:37:52 PM
Uncheck the box next to “Enable Bandwidth Regulation”. The question was meant to ask, “if we un-check that box, will time-based and/or IO-based throttling also turn off?”
The Time-based Throttling /Bandwith Throttling – Limited will be disabled. The IO Throttling has nothing to do with the bandwidth. The IO Throttling has to do with the storage. Disabled “Enable Bandwidth Regulation” shouldn’t affect IO-based throttling.
Enable IO throttling: If a host is handling too many IOs, then the IOs begin to get high latencies. To offset this the VRA
sends fewer concurrent IOs. The latency is measured by taking the average latency for all IOs over a set period of time. For
example, when the period is 5000 milliseconds and the bad IO latency is 40, the average latency is calculated every 5
seconds, and if the average latency exceeds 40, the VRA sends fewer concurrent IOs.
■ Bad IO Latency VM: The threshold above which the latency is considered high, and therefore bad.
■ Requested Duration (ms): The period of time used to measure the average latency