Skip to main content
NetApp Knowledge Base

SRA: Unmapped LUNs may affect device discovery

Views:
700
Visibility:
Public
Votes:
4
Category:
ontap-storage-replication-adapter
Specialty:
virt
Last Updated:

Applies to

  • Site Recovery Manager (SRM)
  • Storage Replication Adapter (SRA) 4.0P1, 7.0, 7.1, 7.2

Issue

When running a device discovery operation in Site Recovery Manager (SRM) the following errors may be seen:


'XmlValidateException' error:

Site Recovery Manager (SRM)

Reviewing the discoverDevices response in the SRM logs shows that no SourceDevice is returned and that an XML parsing error is thrown immediately after the XML output is received:
 

2018-07-11T18:25:11.524Z verbose vmware-dr[06540] [Originator@6876 sub=SraCommand opID=150eed55] discoverDevices responded with:
--> <?xml version="1.0" encoding="UTF-8"?><Response xmlns="http://www.vmware.com/srm/sra/v2" xmlns:replication="http://www.vmware.com/srm/sra30" xmlns:foo="http://www.foo.com/sra/v2">
-->    
-->         <ReplicatedDevices>
-->             <ConsistencyGroups>
-->                 <ConsistencyGroup id="//svm1/CG_vol01" state="read-write">
-->                     <SourceDevices></SourceDevices>
-->                     <TargetGroup key="//svm2/CG_vol01_mirror"></TargetGroup>
-->                 </ConsistencyGroup>
-->             </ConsistencyGroups>
-->             <SourceDevices>
-->                 <SourceDevice id="//svm1/nfs1" state="read-write">
-->                     <Identity>
-->                         <NfsName>/nfs1</NfsName>
-->                     </Identity>
-->                     <TargetDevice key="//svm2/nfs1_dr"></TargetDevice>
-->                 </SourceDevice>
-->             </SourceDevices>
-->             <StoragePorts>
-->                 <StoragePort id="192.168.0.131" type="NFS"></StoragePort>
-->             </StoragePorts>
-->             <TargetDevices>
-->                 <TargetDevice key="//svm1/nfs2_dr"></TargetDevice>
-->             </TargetDevices>
-->         </ReplicatedDevices>
-->         <Warnings>
-->             <Warning code="2067"></Warning>
-->             <Warning code="2067"></Warning>
-->         </Warnings>
-->     </Response>
2018-07-11T18:25:11.529Z error vmware-dr[06540] [Originator@6876 sub=Storage opID=150eed55] XML parsing error in 'buffer' at (6, 52): empty content is not valid for content model '(SourceDevice+)'

 

'Unable to find a matching device' error:

Storage Replication Adapter

Reviewing the discoverDevices response in the SRM logs shows that a peer device could not be found for the device called out in the "Unable to find a matching device" error.  This is despite the fact that the array device is in a healthy snapmirror relationship:

2018-07-30T15:48:26.871Z verbose vmware-dr[03852] [Originator@6876 sub=Storage] Dr::Storage::VmomiLayer::StretchedDatastoreMonitor::PeerArrayPairPropertiesChanged: Received an update for peer array pair MoRef=dr.storage.ReplicatedArrayPair:ec07e4f6-8548-48ce-a00e-58f74467c415:array-pair-2053, local array pair MoRef=[dr.storage.ReplicatedArrayPair:41961a8a-6c85-485f-88bf-68111d5509e1:array-pair-2052], deleted=false, changes=
--> (vmodl.query.PropertyCollector.Change) [
-->    (vmodl.query.PropertyCollector.Change) {
-->       name = "device",
-->       op = "assign",
-->       val = (dr.storage.StorageDevice) [
-->          (dr.storage.StorageDevice) {
-->             id = "//svm2/Unmapped_mirror/unmapped_lun",
-->             name = <unset>,
-->             stretchedStorage = false,
-->             staticSitePreference = <unset>,
-->             peerId = <unset>,
-->             peerName = <unset>,
-->             groupId = <unset>,
-->             groupName = <unset>,
-->             peerGroupId = <unset>,
-->             peerGroupName = <unset>,
-->             role = "target",
-->             targetKey = <unset>,
-->             snapshot = (dr.storage.Snapshot) null,
-->             details = <unset>,
-->             queryDetailsFault = (vmodl.MethodFault) null,
-->             replicationSettings = <unset>,
-->             queryReplicationSettingsFault = (vmodl.MethodFault) null
-->          }
-->       ]
-->    }
--> ]


The 'Unmapped' volume is in a healthy snapmirror relationship:

cluster2::> snapmirror show
                                                                       Progress
Source            Destination Mirror  Relationship   Total             Last
Path        Type  Path        State   Status         Progress  Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
svm1:Unmapped
            XDP  svm2:Unmapped_mirror
                              Snapmirrored
                                      Idle           -         true    -



'No SnapMirror relationship found' error:

When the volume include field is populated in array manager, then the following "No SnapMirror relationship found" error may be seen during device discovery:

Storage Replication Adapter

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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 techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.