Incorrect status 'Failover in Progress' is reported for SRA in SRM

https://kb.netapp.com/mgmt/OTV/SRA/Incorrect_status_'Failover_in_Progress'_is_reported_for_SRA_i…
Updated: Fri, 10 Nov 2023 09:51:54 GMT

Applies to
• Storage Replication Adapter (SRA) 9.x
• Site Recovery Manager (SRM)
• Virtual Storage Consle (VSC)
• ONTAP Tools for VMware (OTV)

Issue
• VMware Site Recovery Manager (SRM) displays an Array Pair device status of Failover In Progress
• This is typically or a relationship that has been failed over to the disaster recovery site and Re-protected
(mirror reverse re-synced) via SRM.
• When observing the NetApp SnapMirror Protection relationships, the mirrors have successfully been reverse

'NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations
provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations
provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or 1
techniques herein is a customers responsibility and depends on the customers ability to evaluate and integrate them into the customers operational
environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this
document.'
 re-synced to the DR location
• SRM placeholder VMs are present in the new target vCenter cluster.
• The Array Pair continues to show Failover In Progress even though the Re-protect has failed

• The SRM logs at SRA stdout section for discoverDevices shows:

Failover occured. Marking the source device as read-only

Cause
• There are stale entries of recently failed over volumes in opt/netapp/vpserver/conf/
devices.txt on SRA
• The Reprotect operation failed to remove the failed over devices from devices.txt

Solution

WARNING

• Do not proceed with the steps unless the Reprotect operation has been attempted and failed with the
symptoms outlined above.
• The NetApp SnapMirror relationships should be replicating back to the DR site and SRM placeholder
• VMs should be present in the DR vCenter cluster

1. Enable SSH access to the VSC Appliance

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 2
 2. Log into the VSC Appliance using the provided credentials.
3. Backup the devices.txt file within the affected VSC/OTV appliance

diag@vscserver:~$ cd /opt/netapp/vpserver/conf
diag@vscserver:~$ sudo su
diag@vscserver:~$ cp devices.txt devices.txt.backup

4. Manually remove the stale devices within devices.txt that appear under the Failover in Progress status
in SRM
5. Return to the Array Pairs window in SRM, and re-run Discover Devices on the relationships showing
Failover In Progress
6. After the discovery completes, the devices will display the correct status

Additional Information

For more information, see the VSC, VASA Provider, and SRA 9.7 Documentation Center

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 3