Add Azure VM to On-primises cluster

• Yogi B

  SSC Enthusiast

  Points: 116

  More actions

  August 25, 2017 at 8:22 am

  #345887

  Hello,

  I am working on a POC in which I need to add a new azure VM as a third node in our existing on-premises 2 node Always ON cluster (On premises and Azure machines are in different subnets). We have site-to-site VPN tunnel setup and when I spin up the VM in azure, I am able to connect to it (Both SQL server and RDP) from our on premises boxes.

  For this POC, we don't have connectivity to our on-premises domain controller hence the Azure VM is a machine in workgroup. I have followed below steps till now:

  • We have a two node cluster in our domain say abc.net.
  • I have added a DNS suffix on the VM created in azure.
  • I have created a local user administrator using the same password that exists on our network.
  • Installed failover clustering feature in Azure VM.
  • Executed Add-ClusterNode powershell command from our primary cluster node.

  At this point it adds the node, keeps on waiting for confirmation that cluster service has started on Azure VM, then it times out and rolls back. Below are the errors event log of azure VM.

  The Cluster service cannot be started. An attempt to read configuration data from the Windows registry failed with error '2'. Please use the Failover Cluster Management snap-in to ensure that this machine is a member of a cluster. If you intend to add this machine to an existing cluster use the Add Node Wizard. Alternatively, if this machine has been configured as a member of a cluster, it will be necessary to restore the missing configuration data that is necessary for the Cluster Service to identify that it is a member of a cluster. Perform a System State Restore of this machine in order to restore the configuration data.

  The Cluster Service service terminated with the following service-specific error:
  The system cannot find the file specified.

  The Cluster Service service terminated unexpectedly.  It has done this 34 time(s).  The following corrective action will be taken in 15000 milliseconds: Restart the service.

  We're using file share witness quoram and we don't have connectivity to that file share from Azure. Also, When I am trying to add a new ip address in cluster for Azure VM, I don't see that subnet listed in ip-address resource.

  Any ideas on how to make that Azure VM subnet visible to existing cluster? Any suggestions or workarounds to complete this POC with limited resources? SQL and windows both are 2016 versions. Thanks in advance.