Validating cluster resource analysis services
To build a 2-node File Server Failover Cluster Instance in Azure, we are going to assume you have a basic Virtual Network based on Azure Resource Manager and you have at least one virtual machine up and running and configured as a Domain Controller.Once you have a Virtual Network and a Domain configured, you are going to provision two new virtual machines which will act as the two nodes in our cluster.
I try to be mindful and shutdown or destroy instances once I am done with them, but occasionally I’ll get pulled away for other business, only to log in the next day and see my credit has expired because I forgot to turn off the VMs.If you read further down that root cause analysis you come across this little nugget. Well, just on February 8th Corey Sanders announced the GA of Managed Disks. https://azure.microsoft.com/en-us/services/managed-disks/ The reason why Managed Disks would have helped in this outage is that by leveraging an Availability Set combined with Managed Disks you ensure that each of the instances in your Availability Set are connected to a different “Storage scale unit”.So in this particular case, only one of your cluster nodes would have failed, leaving the remaining nodes to take over the workload.I don’t think Azure publishes their exact infrastructure, but you can probably assume that behind the scenes they are using Scale Out File Servers for backend storage.So the question is, how could I have survived this outage with minimal downtime?