SRM Reprotect fails with error: Cannot process consistency group (or device) with role 'target' when expected consistency group (or device) with role 'promotedTarget'

Products

• VMware Live Recovery

Issue/Introduction

+ When performing a re-protect task through SRM after failover an error is encountered:

Failed to reverse replication for failed over devices. Cannot process consistency group 'SRM_XXX_XXX' with role 'target' when expected consistency group with role 'promotedTarget'.



+ The error could be a slight different as follows:
(a 'device' could be mentioned instead of 'consistency group' )

Failed to reverse replication for failed over devices. Cannot process device 'xxxxxx" with role 'target' when expected device with role promotedTarget'. 


Environment

VMware Site Recovery Manager 8.x
VMware Live Recovery 9.x

Cause

This error occurs when attempting to reprotect a consistency group in Site Recovery Manager (SRM) and the role of the consistency group is not as expected.

Replication configurations between the primary and secondary sites may not be synchronized.

 

Resolution

In SRM, execute the Discover Devices task on the array pair to retrieve the list of replicated devices and their respective replication directions.

If the replicated device list does not populate or an error occurs during the device discovery process, consult the storage vendor to verify the device status.

Verify the current state and role of the device group on both sites using the storage array management tool or command-line utilities.

Ensure that the replication settings on both sites are consistent and align with the required configurations for SRM.

Once the device group is in the correct role, attempt the reverse replication operation again through SRM.

If the issue persists, engage the storage vendor to investigate the underlying storage array for any additional errors or warnings that could indicate the root cause.

Additionally, verify the SRA (Storage Replication Adapter) and consistency group settings to confirm they are correctly configured. If the problem continues, consider opening a support request with the storage vendor for further assistance.