This article applies to all JSDR software versions.
Problem
The amount of Remaining Background data is not coming down which means Data does not change or decrease over time.
...
Issue
If the remaining background data does not decrease over time, it can indicate the VM I/O is not able to replicate to the Object object store.
In the below scenario, we observed the (remaining BG data) never came down.
...
Let's understand what is Background Replication.
The Background replication is the process of reading existing data from the virtual disk at the protected site and copying it to the recovery site.
...
This issue could happen due to the below reasons
Replication Log volume full
Replication not progressing
Replication is too slow
...
Problems with background replication can be caused by:
Replication Log Volume full
The replication log and metadata have no space left
...
The Replication not processing: The replication is interrupted between DRVA and Object store, check the incoming and outgoing data rate from JetDR UI > Statistics page.
...
.
Replication not progressing
Replication is not processing and becomes stuck due to disruption between the DRVA and object store. This can be checked from the Incoming and Outgoing Data Rate report.
Replication is slow
Replication is slow due to a network bandwidth issue. This can be checked by monitoring the DRVA VM network statistics.
...
...
| Info |
|---|
References: Please refer the below KB if a Replication log volume is full.
Refer to the linked KB article to determine if space on the Replication Log Volume is low. |