This article applies to all JSDR software versions.
Alarm
This alarm is triggered when a specified percentage of operating time data cannot efficiently reach the DRVA causing newly written data to be captured by the IO Filter as “bitmaps” for replication at a later point in time.
Possible Cause
Inefficient data transfer between the DRVA and object store can be caused by:
A network disruption between the DRVA and the object store.
The replication log is full and cannot be written to.
Other factors for the Bitmap mode alarm:
Prolonged bitmap mode Duration alert highlights that respective domain(s) cannot keep up with replication.
When a large VM is added to the domain and its initial sync takes substantial time.
In cases when this alert is raised and there are VMs in initial sync mode, please monitor the amount of bitmap currently required to be replicated for all disks on the domain. While this amount decreases, this alert can be ignored.
Note: Due to current design limitations, bitmap mode impacts the consistency level of the whole domain and affects the RPO. Please make sure that the total amount of bitmap for the domain doesn`t grow unexpectedly.
Resolution:
Verify the DRVA is up and running.
Validate the replication status of the VM/protected domain.
Navigate to the Statistics tab:
Select the protected domain exhibiting the problem.
Examine the Replication graph to identify any performance issues with replication speed.
Ensure there are no connectivity issues between the DRVA and object store.
Ensure there are no errors with the DRVA or replication log.
Check communication between the IO filter and DRVA.
/wiki/spaces/KBDR/pages/2784657420 with MSA logs if you are unable to resolve the issue.