- PDF Free Download

Transcription

1

2 Agenda SQL workloads on Azure Microsoft Azure IaaS concepts Best Practices for SQL running on Azure VMs HA/DR SQL DB HA/DR

3

4 Dedicated Higher cost Shared Lower cost SQL Server Cloud Continuum Hybrid Azure SQL Database Virtualized Databases SQL Server in Azure VM Virtualized Machines SQL Server Private Cloud Virtualized Machines SQL Server Physical Machines High Control High Maintenance Low Control Low Maintenance

5 Azure SQL Database & SQL Server in Azure VM SQL Server in Azure VM Azure SQL Database You access a VM with SQL Server You manage SQL Server and Windows: High Availability, Backups, Patching You can run any SQL Server version and edition Full on-premise compatibility Different VM sizes VM availability SLA: 99.95%: Can achieve higher availability (~99.99%) configuring AlwaysOn Reuse on-premise infrastructure (e.g. Active Directory) You access a DB DB is fully managed: High Availability, Backups, Patching Runs latest SQL Server version, based on Enterprise edition Incomplete on-premise compatibility Different DB sizes and performances (predictable) DB availability SLA: 99.99%

6

7 Executing SQL Server on Microsoft Azure VMs To better execute SQL Server in a Azure VM, you need to understand at least 4 Microsoft Azure layers: Cloud Services Virtual Machines Storage Networking And you will probably need to learn a bit of coding and of powershell

8 A couple of words on: Cloud Services It is a logical container of VMs and/or applications A VM will run inside of the context of a Cloud Service Every Cloud Service has a Virtual Public IP (VIP) Up to 5 Reserved IPs (can be increased) and a FQDN name [CloudServiceName].cloudapp.net You can add many VMs to the same Cloud Service Adding more VMs to the same Cloud Service allows load balancing of specific ports

9 Cloud Services Reserved IPs New-AzureReservedIP ReservedIPName MyWebsiteIP Label WebsiteIP Location Japan West New-AzureVMConfig -Name "WebAppVM" -InstanceSize Small -ImageName $images[130].imagename Add- AzureProvisioningConfig -Windows -AdminUsername $username -Password $password New-AzureVM - ServiceName "MaheshWebApp" -ReservedIPName "MyWebSiteIP" -Location "Japan West"

10 A couple of words on Azure Storage Persistent (Page Blobs) Standard Storage 300 or 500 IOPS per Disk 1 TB per disk VHD format Premium Storage SSD up to 5000 IOPS per Disk (it depends on the space assigned to each disk [e.g. 100gb = 500 IOPS] 1 TB per disk VHD format Not Persistent (Page Blobs) Local Storage Standard or SSD

11 A couple of words on: Azure Storage Standard up to 500TB per sa Locally Redundant, Geo-Redundant, Geo-R with ReadOnly Access 3 copies per datacenter, replica is done on paired data centers Premium up to 35TB per sa Locally Redundant Local (SSD) Storage useful for BPE and TEMPDB

12 A couple of words on Azure VMs A Series Basic Low disks, no autoscaling, Availability SET (Update Domain, Fault Domain) Standard Std Disks, HA & LB D Series (std) 60% faster CPUs than A, local SSD Storage DS Series (std) Premium Storage ready G Series (std) High Memory and bigger storage per VMs Intel E5 v3 CPUs powered

13 SQL Server on Microsoft Azure virtual machines Supports many versions of SQL Server SQL 2014 (Enterprise / Standard / Web) Including a DW-optimized image SQL 2012 (Enterprise / Standard / Web) Including a DW-optimized image SQL 2008 R2 (Enterprise / Standard / Web) Supported versions of Microsoft Windows Windows Server 2012 R2 Windows Server 2012 Windows Server 2008 R2 Near-100 percent compatibility SQL Server failover coming very soon You manage SQL Server Security, backups, high availability, and disaster recovery

14 SQL Server on Azure Virtual Machines A series A0 Shared 768 MB 20 GB 20 GB 1 1x300 1x500 Size CPU Memory A GB 40 GB 70 GB 2 2x300 2x500 A8 Intel Xeon E core da 2,6 GHz DDR MHz 56 GB A GB 60 GB 135 GB 4 4x300 4x500 A3 4 7 GB 120 GB 285 GB 8 8x300 8x500 A9 Intel Xeon E core da 2,6 GHz DDR MHz 112 GB A GB 240 GB 605 GB 16 16x300 16x500 2 NICS: 10GB to Azure services RDMA 32GB Infiniband A GB 135 GB 4 4x500 A GB 285 GB 8 8x500 A GB 605 GB 16 16x500 A GB 382 GB 16 16x500 A GB 382 GB 16 16x500 A GB 382 GB 16 16x500 A GB 16 16x500

15 SQL Server on Azure Virtual Machines D series D GB 50 GB 1 1x500 D2 2 7 GB 100 GB 2 2x500 D GB 200 GB 4 4x500 D GB 400 GB 8 8x500 D GB 100 GB 2 2x500 D GB 200 GB 4 4x500 D GB 400 GB 8 8x500 D GB 800 GB 16 16x500

16 SQL Server on Azure Virtual Machines DS series VM Size CPU cores Memory Max. IOPS Max. Disk Bandwidth STANDARD_DS , MB per second STANDARD_DS , MB per second STANDARD_DS , MB per second STANDARD_DS , MB per second STANDARD_DS , MB per second STANDARD_DS , MB per second STANDARD_DS , MB per second STANDARD_DS , MB per second Premium Storage Disk Type P10 P20 P30 Disk size 128 GiB 512 GiB 1024 GiB (1 TB) IOPS per disk Throughput per disk 100 MB per second * 150 MB per second * 200 MB per second *

17 Azure Virtual Machine G series VM Size Cores Standard_ G1 Standard_ G2 Standard_ G3 Standard_ G4 Standard_ G5 RAM (in GB) Local SSD Storage Persistent Data Disks GB GB ,630 GB ,250 GB ,500 GB 64 Intel Xeon E5 v3 series /us/en/processors/xeon/xeon-e5- solutions.html G-series virtual machines are currently only available in West US and East US 2 regions

18 A couple of words on: Azure Networks You can expose a SQL Server VM on the web using ENDPOINTS (Port redirection, ACL are supported) or a secure connection (VPN, ExpressRoute) Each VM has a Private IP If you set a Virtual Network you can specify subnets (Static IPs available) The VIP is associated to the CS for his lifetime, unless you deallocate it DHCP (infinite lease)/dns are provided by VNETs (you could specify your own DNS) Virtual Networks are bounded to a specific region

19 Microsoft Azure networking architecture 3 2 1

20 VNET to VNET connectivity

21 Azure ExpressRoute

22 Azure Gateways high performance Gateway SKU ExpressRoute Throughput* S2S VPN Throughput * Default ~500Mbps ~80Mbps 10 Max. number of S2S Tunnels PS D:\> New-AzureVNetGateway VNetName MyAzureVNet GatewayType DynamicRouting GatewaySKU HighPerformance High Performance ~1000Mbps ~200Mbps 30

23 - NETWORKING

24 Macro-steps for hybrid configurations Open a Microsoft Azure subscription An available public IP in the on-premises network (needed for Site-2-Site VPN) Point-to-site VPN not supported for advanced SQL Server configurations (e.g. AlwaysOn) On-premises Environment ready (e.g. DNS and Domain Controller) Virtual Network configuration in Microsoft Azure Datacenter selection Set your DNS server on the VNET [highly recommended for Hybrid scenarios] Virtual Gateway configuration IMPORTANT : carefully verify communication between On-Prem and cloud (nslookup, dcdiag, etc.) On-premises VPN config (using VPN device script) Cisco Juniper Windows Server 2012 RRAS (software) Other (E.G. Watchguard, Citrix, F5 )

25 VPN Device info/requirements Static routing A Router with manually configured routing tables VPN s2s only - IKEv1 Pre-shared key ( Encryption algorithms - AES256, AES128, 3DES Hashing algorithms - SHA1 Dynamic routing A router with dynamically configured routing tables VPN s2s and p2s (max 240 clients connected) IKEv2 Pre-shared key for s2s and certificates for p2s Encryption algorithms - AES256, 3DES Hashing algorithms - SHA1

26

27 Connectivity Best Practices Configure Domain Controller Configure a VPN tunnel from on-premises and use on-premises Domain Controller

28 Security Best Practices

29 Performance Best Practices

30 Performance Best Practices (cont.)

31 Storage Spaces (W2012 or W2012R2)

32

33 Why SQL Server high availability? Failure detection for Microsoft Azure virtual machines (not for SQL Server) SQL Server service may be down or hung Servicing of guest operating system causes downtime Servicing of SQL Server causes downtime Healing of Microsoft Azure Services involves restarting virtual machines in different hosts Approximately 12 minutes of downtime each time Upgrades to Microsoft Azure involves servicing the host operating system and restarting virtual machines in the host Approximately 15 minutes of downtime each time

34 Why do we need to configure HA for SQL Server? Storage (Disks) have embedded HA but Single VMs DON T have embedded HA, so a single VM could not be always available in case of Updates/Faults (NO SLA provided with single VMs) Azure provides load balancing features Only few SQL Server services can benefit from AS: e.g. Reporting Services Availability Sets allow VMs to be correctly managed by Azure during planned Upgrades and Updates For traditional SQL Server services you need traditional HA methods

35 A sample configuration

36 HA scenarios Microsoft Azure only AlwaysOn Av. Groups, Mirroring, Log Shipping (Failover Cluster Instances not yet available) Can be INTRA datacenter or between different datacenters

37 AlwaysOn AG between different DCs AlwaysOn & AD/DNS Traffic

38 g-database-mirroring-across-two-windows-azure-datacenters.aspx HA scenarios Hybrid cloud AlwaysOn Av. Groups, Mirroring, Log Shipping VPN not required with certificates

39 39 What s being delivered Wizard to add a replica in a Windows Azure VM Main benefits It takes care of: VM Creation (including data disks and Network Config) Joining VM to Domain and Cluster Adding Node to Availability Group Database backup/restore and AG configuration You need to manually configure the listener 2/06/sql-server-2014-alwayson-availability-groups-addazure-replica-wizard-in-action.aspx - Tutorial On-Premises

40 On-prem network /24 Azure network /24 FRANCEDN5 FRANCEDN2 VPN tunnel RRAS service Virtual Network FRANCEDN4 BACKUP CLIENT FRANCEDN1 Availability Group Windows Cluster VPN Device FRANCEDRRAS AZURE Virtual Gateway FRANCEDN3 Availability Group Windows Cluster REPORT S

41 - ALWAYSON IN HYBRID SCENARIOS - ALWAYSON BETWEEN AZURE DCs

42 AlwaysOn Listener configuration in Hybrid Cloud Step 1- configure endpoint on Azure VMs inside the Cloud Service Hotfix required for win 2008R2/2012

43 AlwaysOn Listener configuration in Hybrid Cloud Step 2- create listener using Failover Cluster manager and add the Dependency Then, manually modify it using powershell

44 AlwaysOn Listener configuration in Hybrid Cloud Step 3- set TCP listener port using SSMS Only one Listener per Cloud Service allowed Troubleshooting guide :

45