1. Deploying Highly Available SQL Server in Windows Azure A Presentation and Demonstration by Microsoft Cluster MVP David Bermingham

2. What is Azure?  “Windows Azure is an open and flexible cloud platform that enables you to quickly build, deploy and manage applications across a global network of Microsoft-managed datacenters. You can build applications using any language, tool or framework. And you can integrate your public cloud applications with your existing IT environment.”

3. Azure IaaS  “Scale on demand, only pay for what you use”  “With Windows Azure, you can spin up new Windows Server and Linux virtual machines in minutes and adjust your usage as your needs change. With our pay-as-you-go approach, you only pay for what you use and there are never any penalties for changing your virtual machine configurations.”

4. SQL on PaaS or IaaS?  Windows Azure SQL Database – Platform as a Service (PaaS) Fully managed relational database service that delivers flexible manageability, includes built-in high availability, offers predictable performance, and supports massive scale-out.  SQL Server in Windows Azure Virtual Machine – Infrastructure as a Service (IaaS) Standard Windows OS and any version of SQL Server, running on a VM in Azure IaaS. Supports “scale-up”

5. SQL on PaaS or IaaS?  Decision Tree  New or existing application/service?  Application/Service requirements Domain joined? SSIS, SSAS, SSRS?  Database Size? 150 GB or larger?  ScaleUp or ScaleOut?

6. Configurations

9. Availability Groups vs. Clusters AlwaysOn Availability Groups AlwaysOn Failover Cluster Support SQL Standard Edition 04 Distributed Transactions 04 Unlimited Databases 04 Automated Client Redirection 24 Protects System Databases (Master, MSDB, etc.) 04 Eases Database Administration 04 Support more than 2-nodes in failover configuration 24 Eliminates SAN as a single point of failure 40 Supports Multisite Clusters 40 Readable Secondary 40

10. Azure Virtual Network  “Windows Azure Virtual Network enables you to create a logically isolated section in Windows Azure and securely connect it to your on-premises datacenter or a single client machine using an IPsec connection. Virtual Network makes it easy for you to take advantage of Windows Azure’s scalable, on-demand infrastructure while providing connectivity to data and applications on-premises, including systems running on Windows Server, mainframes and UNIX. When using Virtual Network you are backed by a 99.9% monthly SLA and have flexibility to enable a range of hybrid IT scenarios.”SLA

11. Create Virtual Network

13. Example of a Network without a VPN connection

14. Editing the Virtual Network Configuring Site-to-Site VPN connectivity

15. Add new DNS Servers As you add new DNS Servers, update your Virtual Network

16. Creating a Site-to-Site VPN

17. Download the VPN Script Configuration Scripts for Cisco, Juniper and Microsoft RRAS VPN devices are downloadable

18. Demonstration Create Virtual Network

19. Create Your First VM

22.  Cloud Service/Cloud Services Name  Region/Affinity Group/Virtual Network  Storage Account  Availability Set  Each server in different “rack”  Power supply  Switch  Servers  99.95% SLA

23. Connect to your VM

24. Demonstration Provision First VM

25. Configure Cluster  Add to VMs to Domain  Enable Failover Cluster Feature  Validate Cluster  Configure Cluster  Add File Share Witness to Quorum  Configure Replicated Storage  Install SQL Into Cluster

26. Add to Domain

27. Enable Failover Cluster Feature

28. Create The Cluster - Validation Start by creating a single node cluster only

29. Create The Cluster – Virtual Cluster Object (VCO) The IP address handed out by DHCP is the same as the physical server, it must be changed before the IP address can come online

30. Create The Cluster – Virtual Cluster Object (VCO) Edit the IP Address Choose an IP address at the end of the DHCP range

31. Create The Cluster – Virtual Cluster Object (VCO) Bring the cluster name resource online after it you change the IP address

32. Create The Cluster – Add The Second Node Validation will warn you about having no shared storage for the quorum disk. Usa a File Share Witness instead

33. Create The Cluster – Add a File Share WItness

34. Quorums in Windows 2012 R2  Dynamic Quorum (introduced in Windows 2012)  Dynamic Witness  Take Away – In Windows 2012 R2 it is ALWAYS recommended to configure a witness, regardless of the number of nodes in the cluster.

35. Demonstration Create The Cluster

36. Create Replicated Storage with DataKeeper Using 3 rd party cluster replication solution, DataKeeper, replicate the data volume(s) between the cluster nodes

37. Install SQL on the First Cluster Node To minimize potential cluster creation problems, use the Advanced Cluster Preparation and Completion options

38. Attach Extra Storage

39. Choose the DataKeeper Volume Resource

40. Specify the Virtual IP Address

41. Add the Second Node to the Cluster

42. Completed Cluster

43. Demonstration Install SQL into the Cluster

44. Configuring AlwaysOn Availability Groups  SQL 2012/2014 Enterprise only  Steps  Install Windows Cluster  Install a Standalone SQL Server 2012  Use the domain account for the SQL service account  Open Port 1433 and 5022 or disable the Windows Firewall  Create a sample database  Set recovery model to Full  Back up this sample database  Enable the AlwaysOn feature on both instances using SQL Server Configuration Manager  Create an Availability Group using the Availability Group Wizard  Create an Availability Group Listener - http://support.microsoft.com/kb/2854082

45. Install Windows Cluster  Same as described in the previous section on Failover Cluster Instance  Install Node1  Fix IP Rsource  Add Node2  Add File Share Witness

46. Change the Service Account The MSSQLServer service account needs to be a domain account

47. Windows Firewall  Open Port 1433 and 5022 or disable the Windows Firewall  1433 – SQL Server  5022 - Replication

48. Enable AlwaysOn High Availability

49. Demonstration Create AlwaysOn Availability Group

50. AG Listener in Azure  The availability group listener is currently only supported on Windows Server 2012 VMs.  The client application must reside on a different cloud service than the one that contains your availability group VMs. Windows Azure does not support direct server return with client and server in the same cloud service.  Only one availability group listener is supported per cloud service because the listener is configured to use the cloud service IP address.

51. AG Listener in Azure  Only configurable in PowerShell  http://www.windowsazure.com/en-us/documentation/articles/install-configure- powershell/  Tutorial  http://msdn.microsoft.com/en-us/library/dn376546.aspx  Automated Script  http://gallery.technet.microsoft.com/scriptcenter/Create-Availability-Group-fff94cd5/

52. Demonstration Create the AG Listener

53. What About Amazon EC2? Windows AzureAmazon EC2 Virtual NetworkVirtual Private Cloud Fault DomainsAvailability Zones Cloud ServiceElastic IP

54. Failover Availability Zone 1 Cluster NodeA Cluster NodeB Block Replication across Availability Zones Block Replication across Availability Zones File Share Witness Availability Zone 2 Availability Zone 3

55. Most Important Thing To Remember  All Cluster IP addresses must be added to the VM as secondary addresses through the EC interface  Each cluster node must reside in a different Availability Zone, which means different subnet as well  Failover across subnets REQUIRES Enterprise Edition of SQL 2012/2014  You must bring your own Enterprise license of SQL Server to the Amazon Cloud

56. Demonstration A Look at Amazon EC