Storage Replication Adapter (SRA): Unable to find matching device -

stale database entries

https://kb.netapp.com/mgmt/OTV/SRA/Storage_Replication_Adapter_(SRA)%3A_Unable_to_find_matc…
Updated: Fri, 10 Nov 2023 09:58:17 GMT

Applies to
• Storage Replication Adapter (SRA) 7.x, 9.x
• Site Recovery Manager (SRM) 8.x (Windows Server)
• Site Recovery Manager (SRM) 8.x (Appliance)

Issue

When running SRA 7.x, 9.x with SRM 8.x, SRM shows error "Unable to find a matching device at the remote site
for the local device" from the Array Pairs section

'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.'
 SRM logs show the following errors

"2020-08-18T10:58:29.748-07:00 info vmware-dr[06980] [SRM@6876 sub=DrTask opID=8e302eb5-

6fb1-44d2-8ec1-7c156d2ecaf9] Task 'dr.storage.ArrayManager.reconfigure1966' failed
--> (dr.storage.fault.CommandFailed) {
--> faultCause = (dr.storage.fault.LocalizableAdapterFault) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> code = "70d7e5fb-4684-49cc-b099-e8f0386c17cb.1003",
--> arg = <unset>
--> msg = ""

Cause

This can be caused by stale entries in the SRA (Derby) database. When a datastore or snapmirror is deleted in
Ontap, SRA holds onto the entries despite running rediscoveries in the Virtual Storage Console GUI and SRM.

NOTE: There are several other causes for the error "Unable to find matching device at local site", e.g. no
snapmirror exists, duplicate volume names, duplicate snapmirror relationship IDs. This article addresses one of
the causes of this error.

Solution
1. If running SRA 9.7P1 or older, upgrade to the latest version of SRA 9.7.1 if able

© 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
 Direct upgrade from any release prior to 9.7 to 9.7P2 or later is not supported. Please upgrade to 9.7 before
upgrading to any later release. Refer to the 9.7 documentation for specific upgrade steps.

2. Check Snapmirrors on both source and destination clusters to see if there are any issues with leftover
relationship IDs from a deleted snapmirror. See KB Storage Replication Adapter: Unable to find matching
device
3. If unable to upgrade, then restart SRA database from SRA maintenance shell
◦ Log in as maint
◦ Choose option 1) Application Configuration then option 9) Hard reset database

If you use VASA VVOLs or custom storage capability profiles, do not perform the following solution. This
solution will not recover the metadata used by VASA Provider and VVOLs. The procedure for resetting the
database when both SRA and VVOLs are used can be found at How to reset VASA Provider and SRA
database

4. Log into the SRM Server and restart the SRM services below

© 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
 5. Perform a re-discovery in Virtual Storage Console by clicking on the "REDISCOVER ALL" button

6. Perform a Device Discovery in SRM by clicking on the "Discover Devices" button

Additional Information
• Issue is tracked in Bug 1128679 "SRA: Rediscovery doesn't clean old entries from SRA Appliance database
as expected"
• Affects SRA releases 9.7P1 and older, patched in SRA 9.7P2
• See KB Storage Replication Adapter: SRA commands run slower than they did at initial setup for further
information on bug work around
• For information on how to perform an in place upgrade or fresh deployment of SRA see Virtual Storage
Console, VASA Provider, and Storage Replication Adapter for VMware vSphere Deployment and Setup
Guide

© 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. 4
 • Similar issue is tracked in KB Storage Replication Adapter: Unable to find matching device

© 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. 5