This article applies to (all JSDR software versions )
\uD83E\uDD14 Problem
This alert is triggered when a domain initiates Backpressure to the replication traffic. JetStream DR effectively manages VM /replication performance by adjusting its operations to accommodate varying network conditions. By understanding and addressing the causes of backpressure, administrators can ensure smoother replication and minimize disruptions/performance impact to protected VMs.
💡 Cause
Backpressure occurs when the rate of incoming data from protected VMs exceeds the available outgoing network bandwidth. This can lead to the replication log filling up or delays in processing the incoming data.JetStream DR triggers this alert when Backpressure is applied.
\uD83C\uDF31 JetStream DR Managing Backpressure
If incoming data exceeds outgoing bandwidth, JSDR uses the replication log temporarily and expects to replicate this data once the spike in VM usage decreases.
If incoming data is excessively high or the replication log is almost full, JSDR applies backpressure to slow down incoming data and prevents the replication log from overflowing and maintains manageable data rates.
If the backpressure limits are exceeded, JSDR switches to bitmap protocol mode. This will allow protected VM to continue its operations by reducing the load on the outgoing replication.
JetStream DR periodically exits bitmap mode to check network performance and returns to regular replication if conditions improve.
This is an automated process requiring minimal to no user intervention when this situation arises. An alert is sent to notify users.