An unexpected error occurred in SRA ""Failed to demote source consistency group 'XXX'. SRA command 'prepareFailover' failed for consistency group 'XX_XXX'..
search cancel

An unexpected error occurred in SRA ""Failed to demote source consistency group 'XXX'. SRA command 'prepareFailover' failed for consistency group 'XX_XXX'..

book

Article ID: 406400

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

  • VMs are replicated using array-based replication (EMC Storage).
  • Following SRA upgrade from 9.x to 10.x, test failover operations may fail with the below error.

    Failed to demote source consistency group 'XXXX'. SRA command 'prepareFailover' failed for consistency group 'XXXX'. An unexpected error occurred in SRA. Please check EmcSrdfSra log file for more information.



In /opt/vmware/support/logs/SRA/sha-***/EmcSrdfSra.log below error will be seen

20250729060109 4753 [20250729060109 4753 [20250729060109 4753 90 Init@SymapiUtilities.cpp
] Initializing SYMAPI session for remote server [10.198.xxx.xxx:2707] 2027 GetInput Devices@SraReplicationGroup.cpp] Performing SymNewCgShow() on CG [XXX] 2038 GetInput Devices@SraReplicationGroup.cpp] [WARNING]: The given group [XXX] is not a CG [20250729060109 4753 2067 GetInput Devices@SraReplicationGroup.cpp] Performing SymDgShow() on CG [XXX] [20250729060109 4753 90 Init@SymapiUtilities.cpp ] Initializing SYMAPI session for remote server [10.198.xxx.xxx:2707] [20250729060109 4753 662 SymmDevListSync@SymapiUtilities.cpp] Performing selective device sync on Symm [000297600539] [20250729060109 4753 687 SymmDevListSync@SymapiUtilities.cpp] The following list of devices are being sync'd [20250729060109 4753 692 SymmDevListSync@SymapiUtilities.cpp] 0009E [20250729060109 4753 692 SymmDevListSync@SymapiUtilities.cpp] 0009F
[20250729060109 4753 698 SymmDevListSync@SymapiUtilities.cpp] Performing SymDevListSync()
[20250729060109 4753 707 SymmDevListSync@SymapiUtilities.cpp] [ERROR]: Failed SymDevListSync() on Symm [000297600539]. [ERROR]: [SYMAPI_C_AUTHZ_NOT_AUTHORIZED: The called is not authorized to perform the requested operation]| [20250729060109 4753 344 setMarker



On the array side, below events will be seen

Record Number         :  1541379    Records in Seq      :        1    Offset in Seq       :        1    Time                : 07/29/25 06:01:08    Vendor ID           :    Application ID      : EmcSrdfSra    Application Version : 10.2.0.1    API Library         : SEK    API Version         : V10.2.0.5 (Edit Level: 2802)    Host Name           : XXXXXXX    OS Name             : WinNT    OS Revision         : 10.0.17763    Client Host         : xxxxxsrm01    Process ID          : 00008320    Task ID             : 00013176    Function Class      : Security    Action Code         : Denied    Text                : Access Denied for User H:b0e1xxxxx\srm, Group=H:b0e1xxxxx\srm, access VIEW (minimum necessary role: Monitor)    Username            : H:b0e1xxxxx\srm    Activity ID         : SEcb7f556464

Environment

VMware Live Recovery 9.x

Cause

After the SRA upgrade, the Docker container ID will change. However, the storage array will continue to have permissions tied to the old container ID. This mismatch will cause an authorization failure when the new container attempts the failover operation.

Resolution

 

  • Update the storage array configuration to grant the necessary permissions to the SRM user associated with the new container ID.

  • After applying the necessary permissions, proceed to re-run the test/actual failover which should complete successfully. 

 

Powered by Wolken Software