Disaster recovery or planned migration fails on VMware Live Site Recovery with error "remote copy group is currently busy"

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• On running Recovery (Planned Migration or Disaster Recovery), VM fails to recover and throws following error:
  
  ERROR:

  Operation Failed

  Failed to promote replica devices. Failed to promote replica consistency group '###############'. SRA command 'failover' failed for consistency group ''###############'. Failed to Fetch Volume export information from the array. Error: ######### (errors.errorString=Failed to Identify the Specified Host Export Information from the XML)

  Verify the connections and retry

  Operation ID: ########-####-####-####-############

• Recovery failed at step-13 of Recovery workflow "Change recovery site storage to writable"
  
  
• 'HPE Alletra 6000 and Nimble Storage Replication Adapter for VMware SRM' is the SRA deployed.

Environment

VMware Site Recovery Manager 8.8

Cause

• Consistency Group  on storage array corresponding to the Protection Group is reported to be busy while running Recovery and thus error -- "Remove copy group is currently busy". 
  
  (from /opt/vmware/support/logs/srm/vmware-dr.log):

YYYY-MM-DDTHH:MM:SS.### error vmware-dr[####] [SRM@6876 sub=AbrRecoveryEngine opID=########-####-####-####-############-failover:####:####:####:####] ProcessFailoverResult: Failed to promote replica devices for group 'vm-protection-group-#####' using array pair 'array-pair-####': (vmodl.MethodFault) [
-->    (dr.storageProvider.fault.StorageDeviceGroupFailoverFailed) {
-->       faultCause = (dr.storage.fault.CommandDeviceGroupFailed) {
-->          faultCause = (dr.storage.fault.SimpleAdapterFault) {
-->             faultCause = (vmodl.MethodFault) null,
-->             faultMessage = <unset>,
-->             description = "Failed to perform failover operation due to error : remote copy group is currently busy",
-->             fixHint = "Make sure the remote copy group is configured correctly on storage system and retry the workflow."
-->             msg = ""
-->          },
-->          faultMessage = <unset>,
-->          commandName = "failover",
-->          deviceGroup = "#########"
-->          msg = ""
-->       },
-->       faultMessage = <unset>,
-->       deviceGroup = "##########"
-->       msg = ""
-->    }
--> ]

Resolution

Involve storage vendor to investigate on why remote copy of replicating pair reports busy.