Windows Server 2022 Failover Cluster on Simplivity 4.x

[AALRR]

Windows Failover Clustering / WSFC / CAB

How do I find the best practice guide to setup Windows Server 2022 cluster failover between two VM’s on Simplivity 4.2 with VMware 7.x?

The only guide I can find, is related to Windows Server 2016, Simplivity 3.x, and VMware 6.5 (https://www.hpe.com/psnow/doc/a50000833enw)

I have tried using this guide on our setup with these settings pr. VM:

• SCSI bus sharing: Virtual
• Type: LSI Logic SAS
• Disk Provisioning: Thick provision lazy/eager zeroed
• Disk mode: Independent Persistent

But it results in error related to “Validate SCSI-3 Persistent Reservation”, in the Microsoft Failover Cluster Validation.

Errors from the Microsoft Failover Cluster Validation report:

Node VM01.xxx.local successfully issued call to Persistent Reservation RESERVE for Test Disk 0 which is currently reserved by node VM02.xxx.local. This call is expected to fail.

Test Disk 0 does not provide Persistent Reservations support for the mechanisms used by failover clusters. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters.

We have multiple Windows Failover Clusters running Windows Server 2016 with same VM config, but they were configured with older VM hardware version, and on Simplivity 3.x version.

I hope someone can help us in the right direction.

[gustenar]

Hello @AALRR, 

It seems that we don't have an updated document at the moment. I will look and see if I can find anything that can help with your issue. 

[AALRR]

I am still looking forward to receiving the new documentation on this.

[LuisSoares]

Provisioning type of the VMDK disk needs to be: "Disk Provisioning: Thick provision lazy/eager zeroed"

[AALRR]

Hi @gustenar ,
Is this a HPE validated solution? Can it be find in any documentation or do you have this working in production today?

[gustenar]

Hello @AALRR 

I've made the request to update the document as soon as possible, it is still a work in progress. Unfortunately, I don't have this setup in production at the moment.