Page Comparison

\uD83E\uDD14 Problem

...

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 object store. This may Failure to connect to the replication log can interrupt replication and recovery processes , thereby compromising the DR operation and failure of ongoing recovery operations.

...

\uD83C\uDF31 Solution

...

Check the details of the domain to determine which DRVA is connected to the problem domain.

...

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

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

   RL

   • 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. If the RL Disk is detached, re-attach it again.

5. Validate DRVA access to Datastore.

6. The user can reboot the DRVA and check the statusEnsure there are no underlying issues with the data store where the replication log disk is provisioned.

7. If the replication log disk is found to be detached from the DRVA, re-mount the disk.

8. 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.

9. Reboot the DRVA and then check its status.