I would like to setuo a generic service on a windows 2016 failover cluster but can see there are some issues with shared storage,additional network cards and ip addresses on Azure, is it supported on Azure with sever 2016 and is there any guides on setting up faiover clustering, I an see there are plenty of guides on setting up SQL but that seems to manage the storage itself.
Azure Windows 2016 Failover cluster
azurefailoverclusterwindows-cluster
Related Solutions
I did exactly what you did - I was adding a new node to an SQL 2014 AlwaysOn cluster and I forgot to uncheck the "Add Storage" button at the end of the wizard.
To get the storage back, and your cluster online:
- Remove all the disks "Cluster Shared Volumes" (Right-click,
Remove from Cluster Shared Volumes) - Remove all the disks from the cluster completent (Right-click,
Remove, "Yes") - Wait for a few minutes for each node in the cluster to remove its disks from being "in the cluster"
- On each node in the cluster, put each disk that is now offline, back online (this can be a slow and annoying process when doing this to remote servers on the far end of a slow WAN. Hope you don't have too many).
- Start the SQL Server service on all the affected nodes (don't forget the SQL Server Agent service as well)
For bonus points
- Pray this wasn't a production cluster
- Smack yourself repeatedly so you remember to always uncheck the button to add cluster storage in the cluster wizard
To my mind this basically means that the failover was caused by the fact that File Share Witness gone offline. But - why?
That's not what it means. Reading through the logs that were posted, I can see the core cluster group failed to another node (in hopes that it fixes the connectivity issue with the witness), however there is nothing in regards to SQL Server. You'll need to find where in the logs SQL Server had the failure and trace it back to see why the cluster decided to initiate an automatic failure.
The fact that an automatic failure occurred means the cluster had quorum. If it didn't, the automatic failure wouldn't have happened.
And we're wondering are there ways to fix this behaviour. Any clarification or advice is welcome, thanks!
Nothing to fix as this isn't what's happening. Look into the log to see what the reason for the automatic failure was, that's why it failed - not because it couldn't health check the FSW.
Best Answer
Sam is right. You can build Failover Cluster and configure high availability for your application using either S2D which is officially supported in Azure or third-party HA shared storage solutions, for example, StarWind Virtual SAN. The resulting highly-available CSV can be used for virtual machine files and as a backend storage for File Server SMB shares.