When using EMC RecoverPoint SRA, the test failover operation fails
search cancel

When using EMC RecoverPoint SRA, the test failover operation fails

book

Article ID: 309558

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Symptoms:
  • When using EMC RecoverPoint Storage Replication Adapter (SRA) in a Site Recovery Manager (SRM) environment, the test failover operation fails
  • The SRM Recovery plan execution sequence displays this error:

    Non-fatal error information reported during execution of SRA:testfailover:Output

  • You see this warning:

    WARNING: testFailoverStart action: consistency group TEST_CG is not in Auto SRM mode thus SRM can not perform operations on it during that time. SRM can perform operation on consistency groups only in Auto SRM mode. Please fix the group's Policy

  • In the RecoverPoint SRA log within the SRM logs, you see messages similar to:

    [2010-07-28 09:58:39.004 00756 verbose 'SysCommandLineWin32'] Starting process: "C:\\Program Files (x86)\\VMware\\VMware vCenter Site Recovery Manager\\external\\perl-5.8.8\\bin\\perl.exe" "C:/Program Files (x86)/VMware/VMware vCenter Site Recovery Manager/scripts/SAN/array-type-recoverpoint/command.pl"
    [2010-07-28 09:58:41.389 00756 trivia 'SecondarySanProvider'] testFailover's output:
    Log location: /tmp/santorini.log
    [#5]
    [#5] Log mode: false
    [#5]
    [#5] Wed Jul 28 09:58:39 EDT 2010 FINE: got the following command from SRM:
    [#5] <Command xmlns="</SPAN> http://www.emc.com/santorini/do/command ">
    [#5] <Name>testFailover</Name>
    [#5] <ConnectSpec>
    [#5] <Name>RecoverPoint</Name>
    [#5]
    192.168.4.20

    [#5] <Username>admin</Username>
    [#5] <Password>***</Password>
    [#5] </ConnectSpec>
    [#5] <Action>start</Action>
    [#5] <ArrayId>RecoverPoint-DR_SiteB</ArrayId>
    [#5] <InitiatorGroupList>
    [#5] <InitiatorGroup id="iScsi-fc-all">
    [#5] <Initiator id="50:01:43:80:02:a3:00:b0" type="fc"/>
    :
:
[#5] <Initiator id="50:01:43:80:02:a3:00:da" type="fc"/>
[#5] </InitiatorGroup>
[#5] </InitiatorGroupList>
[#5] <LunAccess>
[#5] <ReplicaLun key="60:06:01:60:C9:00:27:00:A2:7E:E5:26:69:33:DF:11">
[#5] <InitiatorGroup id="iScsi-fc-all"/>
[#5] </ReplicaLun>
[#5] </LunAccess>
[#5] <ReplicaLunKeyList>
[#5] <ReplicaLunKey>60:06:01:60:C9:00:27:00:A2:7E:E5:26:69:33:DF:11</ReplicaLunKey>
[#5] </ReplicaLunKeyList>
[#5] <SplitReplication>false</SplitReplication>
[#5] <OutputFile>C:\Windows\TEMP\vmware-SYSTEM\dr-sanprovider756-0</OutputFile>
[#5] <LogLevel>trivia</LogLevel>
[#5] </Command>
[#5] Wed Jul 28 09:58:39 EDT 2010 INFO: Starting to run: Test Failover command with true action on replica LUN list [60:06:01:60:C9:00:27:00:A2:7E:E5:26:69:33:DF:11] on storage array ID RecoverPoint-DR_SiteB.
[#5] Wed Jul 28 09:58:39 EDT 2010 FINE: Logic testFailoverStart called for luns: [60:06:01:60:C9:00:27:00:A2:7E:E5:26:69:33:DF:11]
[#5] Wed Jul 28 09:58:39 EDT 2010 FINE: mapping the following luns wwn: [60:06:01:60:C9:00:27:00:A2:7E:E5:26:69:33:DF:11] to cg names
[#5] Wed Jul 28 09:58:41 EDT 2010 FINE: mapLunsToGroupNames found the following groups: [TEST_CG]
[#5] Wed Jul 28 09:58:41 EDT 2010
WARNING: testFailoverStart action: consistency group TEST_CG is not in Auto SRM mode thus SRM can not perform operations on it during that time. SRM can perform operation on consistency groups only in Auto SRM mode. Please fix the group's Policy
[#5] Wed Jul 28 09:58:41 EDT 2010 INFO: Returning xml output file:
[#5] <Response xmlns="</SPAN> http://www.emc.com/santorini/do/failover ">
[#5] <ReturnCode>4</ReturnCode>
[#5] <ReplicaLunList/>
[#5] </Response>
[2010-07-28 09:58:41.390 00756 info 'SecondarySanProvider'] testFailover exited with exit code 0
[2010-07-28 09:58:41.390 00756 trivia 'SecondarySanProvider'] 'testFailover' returned <Response xmlns="</SPAN> http://www.emc.com/santorini/do/failover ">
[#5] <ReturnCode>4</ReturnCode>
[#5] <ReplicaLunList/>
[#5] </Response>
[#5]
[2010-07-28 09:58:41.391 00756 info 'SecondarySanProvider'] Return code for testFailover: 4
[2010-07-28 09:58:41.391 00756 error 'SecondarySanProvider'] The scripts returned an error, leaving the temporary file 'C:\Windows\TEMP\vmware-SYSTEM\dr-sanprovider756-0'
[2010-07-28 09:58:41.391 00756 error 'SecondarySanProvider'] Unknown error encountered by the script


Environment

VMware vCenter Site Recovery Manager 4.0.x
VMware vCenter Site Recovery Manager 4.1.x

Resolution

This issue occurs if the SRM support policy setting Use SRM is disabled. The Use SRM option must be enabled for the RecoverPoint SRA to work properly during test failover and failover operations.
To resolve this issue, enable the Use SRM option.
To enable the Use SRM option:
  1. In the RecoverPoint GUI, click Starting Replication > Configuring replication policies > Configuring group policies.
  2. Enable Use SRM.
For more information on the SRM Support Policy settings:
  • Contact EMC technical support.
  • See the Consistency Group Stretch Cluster / SRM Support Policy Settings section of the EMC RecoverPoint Administrator's Guide.

    To access the EMC RecoverPoint Administrator's Guide, you must be a registered Powerlink user.
Note: The preceding link was correct as of September 24, 2010. If you find the link is broken, provide feedback and a VMware employee will update the link.