To avoid unnecessary cluster node failovers due to system disk I/O latency, virtual disks must be created using the EagerZeroedThick format on VMFS volumes only, regardless of the underlying protocol.
Note: Although EagerZeroedThickVMDKs can be created on VAAI-capable NAS arrays using a suitable VAAI NAS plug-in, NFS is not a supported storage protocol with Microsoft Clustering. Exception to this note is footnote 6 under table 1 notes above.
0
0
genjam.bhaisays:
C & D is correct.
Microsoft Cluster Service (MSCS)
A typical clustering setup includes:
* Disks that are shared between nodes … the shared disk must be on a Fibre Channel (FC) SAN, FCoE or iSCSI.
* A private heartbeat network between nodes.
C and D.
NFS not supported.
1
0
c & D
0
0
C & D
https://kb.vmware.com/s/article/2147661?other.KM_Utility.getArticleLanguage=1&r=1&other.KM_Utility.getArticleData=1&other.KM_Utility.getArticle=1&ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1&other.KM_Utility.getGUser=1
0
0
To avoid unnecessary cluster node failovers due to system disk I/O latency, virtual disks must be created using the EagerZeroedThick format on VMFS volumes only, regardless of the underlying protocol.
Note: Although EagerZeroedThickVMDKs can be created on VAAI-capable NAS arrays using a suitable VAAI NAS plug-in, NFS is not a supported storage protocol with Microsoft Clustering. Exception to this note is footnote 6 under table 1 notes above.
0
0
C & D is correct.
Microsoft Cluster Service (MSCS)
A typical clustering setup includes:
* Disks that are shared between nodes … the shared disk must be on a Fibre Channel (FC) SAN, FCoE or iSCSI.
* A private heartbeat network between nodes.
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.mscs.doc/GUID-674A9161-9AF9-4746-8D7B-8C7795A1FB49.html
4
0