Skip to main content
NetApp Knowledge Base

SnapMirror active sync (formerly SM-BC) failover completes but SAN hosts remain connected to source LUNs

  1. Last updated
  2. Save as PDF
Views:
424
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • SnapMirror Business Continuity (SM-BC)
  • SnapMirror active sync 

Issue

  • Snapmirror failover start was done a week ago but failover did not occur and source LUNs still being written to a week after attempted failover
  • Replication is successfully failed over to the DR site but SAN hosts remain connected to source site LUNs
  • All SM-BC mirrors reporting  as "In-Sync" now with the original source as the destination
  • Source volumes are now type DP and DR volumes now RW as expected
  • Customer then unmaps the LUNs on original source and the clients lose connectivity to the LUNs until they remapped the source LUNs

WARNING

When using Windows Server host mappings Do not failover and delete the SM-as relationship / consitency groups from the alternate array. This will lead to Microsoft MPIO corrupton.

 

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.