VLCR Snapshots Fail or Hang Due to High Connector Latency
Article ID: 438173
Updated On:
Products
Issue/Introduction
VMware Live Cyber Recovery (VLCR) snapshot tasks fail with the error: "Snapshot for protection group failed. Could not snapshot any VM." Alternatively, snapshot tasks may remain stuck at 5% or 20% for several hours. The VLCR UI dashboard reports slow throughput (e.g., 5.8 - 7.2 MB/s).
Environment
VMware Live Cyber Recovery (VLCR) all versions
Cause
Misconfigured DNS settings on the local network firewall cause severe latency and low throughput between the on-premises VLCR Connector and the cloud filesystem. This latency leads to a massive buildup of CLOSE-WAIT TCP sessions on the connector, ultimately causing snapshot tasks to hang and fail.
Resolution
Verify and correct the DNS configuration on the local network firewall to ensure traffic from the VLCR connector is resolved and routed without excessive latency.
Cancel any pending or stuck snapshot jobs from the VLCR UI.
Monitor the connector throughput. If the environment is stable but throughput limits are reached due to data volume, deploy an additional VLCR connector to distribute the load.
Additional Information
To deploy a new connector, refer to the following documentation :
Feedback
