2 Node Windows File Server Cluster

[preecy]

We recently purchased a HPE Nimble solution consisting of: 1 x HF40, 3 x DL360 Gen10 and a pair of M-Series switches. As we're new to HCI/Nimble, we used the HP installation services. HP set up the switches, storage array and the three ESXi servers. They also created a new vCentre v7 deployment for us too.

Out current setup consists of: 3 x P4350 SANs, 3 x DL360 Gen8 and a couple of ProCurve switches. We're running vSphere 6 on this setup.   

We've started to migrate vm's over to the new vCentre. Rather than using LUNs/VMFS volumes as we did with our old setup, we've gone with VVOLs this time around. The plan is to decommission the old vSphere v6/harware once all vm's are migrated.

We also have a physical HP StoreEasy server which is now EOL. The StoreEasy is our primary Windows File Server and we want to decommission this too. We plan to deploy two new vm's, in a two node Windows File Server Cluster setup, on the new vSphere datacentre.  I'm struggling to find any best practices or guidance based on WSFC, on vSphere7 and running on Nimble. Has anyone setup anything simlar or have any suggestions?

[support_s]

System recommended content:

1. Microsoft Windows Server 2008 R2 - Cluster Node 1 Lost Communication with Cluster Node 2

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[HTTH · Accepted solution]

We recently just setup a MS cluster in VMware 7 with shared disks on a vVol datastore in Nimble.  The cluster has 2 VMs hosted on different hosts.  The main guide is here https://docs.vmware.com/en/VMware-vSphere/7.0/vsphere-esxi-vcenter-server-70-setup-wsfc.pdf.

Points:

• Makre sure all vCenter and host certificates are valid
• VASA Provider must be enabled on Nimble side
• vCenter > Configure > Storage Providers: you should see the Nimble Array (https://array-ip:8443/vasa/version.xml) here.  If not, add by following this https://community.hpe.com/t5/Array-Setup-and-Networking/Creating-vVOLS-with-Nimble-Connection-Manager/td-p/7013642#.Yv5vRRzMJHa
• On Nimble side, create a new folder (see link above).  Or you can do this in vCenter: Nimble Actions > Create VVol Datastore.  Give it time before you can see the vVol folder in Nimble.

Then you can follow the guide from VMware to create the cluster.  The guide does not mention but I found that in my case the VMs must use VMXNET 3 for network adapter for the cluster to work.

Hope this helps.

[preecy]

Thanks, that guide was exactly what i was looking for.
I've now deployed two vm's running Win2022 with an anti-affinity rule to ensure both vm's are kept on separate hosts. I've then created a shared vmdk and setup WSFC. The WSFC validation has passed all tests and i've successfully deployed a clustered file server. Just testing it all now but appears to be working well.
Thanks again.

[Sunitha_Mod]

Hello @preecy, 

Excellent!

Glad to know the problem has been resolved.