Knowledge Base

If there is a temporary interruption in the VMware Channel, or there is insufficient channel bandwidth to cope with the current volume of replication traffic, the active server queue may begin to fill. If the situation persists, the size of the queue may eventually exceed the configured disk quota.

If the VMware Channel is slow and a queue buildup is repeatedly experienced, measure the available and needed bandwidth and, based on Heartbeat Diagnostics measurements, increase the bandwidth to accommodate all the changes during a peak day.

If the VMware Channel is having trouble keeping up when server or application maintenance tasks are running, reschedule the maintenance tasks so that they start at different times during the maintenance period, allowing 10-15 minutes between two consecutive tasks. Additionally, check if there are any task configuration settings which can be adjusted to reduce the disk I/O during the maintenance tasks.

A less desirable option is to measure the amount of data generated and, based upon the measurements, increase the size of the queue accordingly.

Caution: By simply increasing the size of the affected queue, if a failover occurs, the volume of data at risk is also increased. Before adjusting the queue size, review your Recovery Point Objective (RPO) to ensure that the volume of potential data loss as the result of the failover is within your RPO.