DR Store IO Error

This article applies to all JSDR software versions.

Alarm

This alarm signals a problem accessing the replication log volume of a DRVA. The replication log is a critical component for storing live recovery data and replicating it to the object store. Failure to connect to the replication log can interrupt replication and recovery processes thereby compromising DR and recovery operations.

Possible Cause

Connectivity issues between the DRVA the replication log can be caused by:

• Replication log storage is offline or disconnected from the DRVA.
• Configuration errors with the JetStream DR setup.
• Data store permissions or access control issues.

Resolution

Collect the MSA support bundle before proceeding with the following steps:

1. Identify the DRVA being used by the protected domain experiencing the problem.
2. Validate the replication log disk is visible to the DRVA (using the lsblk command from the DRVA console).
   • Then navigate to the DRVA VM → Edit settings and check if the replication log disk is attached.
3. Validate DRVA access to the data store.
   • Test this by creating a new replication log for the DRVA on the data store.
4. Ensure there are no underlying issues with the data store where the replication log disk is provisioned.
5. If the replication log disk is found to be detached from the DRVA, re-mount the disk.
6. Ensure the replication log disk has not been deleted from the data store.
   • If so, the VMs will need to be re-protected using another healthy protected domain/DRVA.
7. Reboot the DRVA and then check its status.

Contact Jetstream Support with MSA logs if you are unable to resolve the issue.