Disks marked as reserved/unavailable while using SM-BC with Windows Failover cluster
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.
- Windows end reports the disk as "
ArbitrateFailure
", which indicates PR table issue on target.