Skip to main content
NetApp Knowledge Base

Disks marked as reserved/unavailable while using SM-BC with Windows Failover cluster

Views:
451
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9.12.1x
  • SnapMirror for Business Continuity (SM-BC)
  • Windows Failover cluster configuration on Hyper-V cluster.

Issue

  • The Clustered disk becomes "unavailable" for the Windows Failover cluster if they are protected with SM-BC.
  • Disks goes into  "reserved" on the windows cluster hyper v host while doing snapmirror initialization on NetApp.
  • Windows Failover cluster Configuration being used on the host end.
  • "Reservation conflicts" are reported in perf archives collected covering the issue time.

reservationconflict.png

  • Windows end reports the disk as "ArbitrateFailure",  which indicates PR table issue on target.

Arbitrate failure.png

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.