Create writable storage snapshot fails with error: "TestFailover for the volume peer-of-#-#-#-#-#:LUNX on the array X is already in progress."

Products

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

Issue/Introduction

• A Test Failover fails and the following error is seen in SRM/VLSR UI
  • Failed to create snapshots of replica devices. Failed to create snapshot of replica device peer-of-#-#-#-#-#:LUNX. SRA command 'testFailoverStart' failed for device 'peer-of-#-#-#-#-#:LUNX'. TestFailover for the volume peer-of-#-#-#-#-#:LUNX on the array X is already in progress.
• SRM/VLSR vmware-dr.log may show
  • 2025-08-13T01:48:28.733Z error vmware-dr[02869] [SRM@6876 sub=AbrRecoveryEngine opID=X-X-X-X-X-test:X:X:X:X] ProcessFailoverRe
sult: Failed to create snapshots of replica devices for group 'vm-protection-group-#' using array pair 'array-pair-#': (vmodl.MethodFault) [
-->    (dr.storageProvider.fault.StorageDeviceTestFailoverStartFailed) {
-->       faultCause = (dr.storage.fault.CommandDeviceFailed) {
-->          faultCause = (dr.storage.fault.LocalizableAdapterFault) {
-->             faultCause = (vmodl.MethodFault) null,
-->             faultMessage = <unset>,
-->             code = "#-#-#-#-#.1013",
• Storage Replication Adapter logs may report

  • [08/13/2025 01:48:28,FailoverHelper.cs:HandleTestFailover,V] Querying array for volume LUNX.
[08/13/2025 01:48:28,FailoverHelper.cs:HandleTestFailover,V] Volume LUNX exists on array #-#-#-#-#
[08/13/2025 01:48:28,FailoverHelper.cs:HandleTestFailover,E] Volume LUNX already exists on X. Failing the testFailover of this volume.

    <TestFailoverStartResults>
    <TargetDevices>
      <TargetDevice key="peer-of-#-#-#-#-#:LUNX">
        <Error code="1013">
          <vendor_x:VolumeName>peer-of-#-#-#-#-#:LUNX</vendor_x:VolumeName>
          <vendor_x:ArrayName>X</vendor_x:ArrayName>
        </Error>
      </TargetDevice>
    </TargetDevices>
  </TestFailoverStartResults>
</Response>

Environment

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

Cause

Some array Storage Replication Adapters (SRA) may have source volume and replicated volume/snapshot naming convention requirements between array pairs.  If these conventions are not followed, the SRA may believe the replicated volume snapshot, that is being promoted for the test, is conflicting with the original source volume in the array pair.

Resolution

• Storage Replication Adapter (SRA) engagement is recommended.
• Adding a suffix or prefix to all the replicated LUNs on one array, source or destination, may eliminate the conflict thus resulting in successful Test Failovers.  SRA vendor engagement is recommended if clarity is required.