SRM Test Recovery Failed with SRA command testFailoverStart failed error.
search cancel

SRM Test Recovery Failed with SRA command testFailoverStart failed error.

book

Article ID: 390367

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Failed to create snapshots of replica devices. SRA command testFailoverStart failed. Failed to identify the protocol type of target group 'Group_Name' access groups. Make sure all the protected site devices protocol is updated in VOLColl metadata. Trigger Test with sync once before running RUN operation.

 

SRA log  shows entries that look similar to:

2025-02-24 20:26:46.974 UTC]  [ERROR]  [GID:1]  ( createvolcollprotomap.go commands/testfailoverstart/nimble.(*CreateVolcollProtoMap).Handle 60 )  HPESRA: Failed to get proto type of volume collection Group_Name
[2025-02-24 20:26:46.976 UTC]  [INFO]  [GID:1]  ( testfailoverstarthandler.go commands/testfailoverstart.(*TFSHandler).execute 72 )  HPESRA: Test Failover Star command failed
[2025-02-24 20:26:46.978 UTC]  [INFO]  [GID:1]  ( responsebuilder.go commands/responsebuilder.(*sraResponseBuilder).WriteResponse 122 )  HPESRA: XML Response for command testFailoverStart :
 <?xml version="1.0" encoding="UTF-8"?>
  <Response xmlns="http://www.vmware.com/srm/sra/v2">
      <Error>
          <Description>Failed to identify the protocol type of target group 'Group_Name' access groups.</Description>
          <FixHint>Make sure all the protected site devices protocol is updated in VOlcoll metadata. Trigger Test(with sync) once before running 

Environment

vSphere Live Site Recovery 9.0.2 and HPE SRA

Resolution

1) Run SRM Test Recovery by selecting 'Replicate recent changes to recovery site'. (Selecting this check box ensures that the recovery site has the latest copy of protected virtual machines, but means that the synchronization might take more time). See the reference document for performing a test Test a Recovery Plan

2) Perform a cleanup. See the reference document for cleanup Clean up After Testing a Recovery Plan

3) Run the test recovery again without selecting 'Replicate recent changes to recovery site'.