Critical SQL Server Databases:

Transcription

1 Webinar Critical SQL Server Databases: Provide HA with SQL Server Failover Clustering and Cluster Shared Volumes

2 Edwin Sarmiento Microsoft MVP/Microsoft Certified Master: rmiento

3

4 high availability

5 high availability characteristic of a system that is f u l l y o p e r at i o n a l for a long period of time

6 high availability is NOT the same as UPTIME

7 Just because something is UP doesn t mean it s available available

8 high availability Recovery Time Objective (RTO) When is my application coming back?

9 high ZERO downtime

10 downtime 90 (one nine ) 36.5 days per year 72 hours per month % availability 16.8 hours per week

11 downtime 99 (two nines ) 3.65 days per year 7.2 hours per month % availability 1.68 hours per week

12 downtime 99.9 (three nines ) 8.76 hours per year 43.8 minutes per month % availability 10.1 minutes per week

13 downtime % availability (four nines ) per year minutes 4.32 minutes per month 1.01 minutes per week

14 downtime (five nines ) 5.26 minutes per year 25.9 seconds per month % availability 6.05 seconds per week

15 downtime How long does it take to restart SQL S e r v e r % availability (five nines ) 5.26 minutes per year 25.9 seconds per month 6.05 seconds per week

16 Cost Availability/RTO versus Total Cost of Ownership Time

17 high ZERO downtime

18 high availability features

19

20 ALWAYSON AVAILABILITY GROUPS

21 *DATABASE (group) protection ALWAYSON AVAILABILITY GROUPS introduced in SQL Server 2012

22 *DATABASE (group) protection ALWAYSON AVAILABILITY GROUPS can either be an HA and/or DR solution

23 ALWAYSON AVAILABILITY GROUPS combination of DATABASE MIRRORING & FAILOVER CLUSTERING

24 *maximum of EIGHT replicas Windows Server Failover Cluster Database Mirroring Primary Replica SQL Server Secondary Replica SQL Server Secondary Repli SQL Server log data log data log data

25 challenge Availability Group requires SQL Server Enterprise Edition

26 FAILOVER CLUSTERING

27 FAILOVER CLUSTERING can either be an HA and/or DR solution *INSTANCE protection

28 Windows Server Failover Cluster failover how it works clustering SQL Server 2-node cluster t r a d i t i o n al log data

29 Windows Server Failover Cluster failover Application clustering how it works SQL Server t r a d i t i o n 2-node cluster al log data

30 cluster shared SQL Server volumes * shared disks containing an NTFS or ReFS volume that is made accessible for read and write operations by all nodes of WSFC we will only focus on Windows Server Windows Server Failover Cluster

31 Windows Server Failover Cluster SQL Server let s look at failover in the context of the storage

32 Windows Server Failover Cluster SQL Server the storage is owned by only one cluster node at a time I/O workload only goes thru that single path to the storage

33 Windows Server Failover Cluster AD/DNS SQL Server during failover, the storage gets logically dismounted from the failed node and remounted on the new active/primary node

34 Windows Server Failover Cluster AD/DNS SQL Server the amount of time it takes to bring the storage online depends on how long it takes to mount the storage to the new active/primary node

35 Windows Server Failover Cluster SQL Server with CSV, there are now multiple paths to the storage I/O workload can be routed thru different paths to the storage

36 Windows Server Failover Cluster SQL Server with CSV, no need to remount storage on new active/primary node after failover this reduces downtime, increases resiliency and reliability

37 Windows Server Failover Cluster SQL Server with CSV, no more 23 drive letter limitations this means you no longer have to memorize the alphabet in terms of failover cluster drives

38 with CSV, the concept of SQL Server exclusive ownership of storage is redefined *this means that SQL Server failover clustered instances no longer has a direct dependency on the shared drive to come online Windows Server Failover Cluster

39 Windows Server Failover Cluster SQL Server failover Application clustering how it works *can be implemented with SQL Server Standard Edition t r a d i t i o n 2-node cluster al log data

40 Windows Server Failover Cluster SQL Server failover Application clustering how it works *can be implemented with SQL Server Standard Edition log data log data t r a d i t i o n 2-node cluster al HA

41 What does StarWind Virtual SAN change? StarWind Virtual SAN turns local storage into fault tolerant CSV for the local SQL cluster

42 Benefits compared to native clustering Deployment price is reduced ~3 times Maximized performance because of short IO path Disk, RAM, and Flash FT without Enterprise SQL licensing

43 Configure SQL Server 2014 Failover Clustered Instances to use Cluster Shared Volumes demo

44 Edwin Sarmiento Microsoft MVP/Microsoft Certified Master: rmiento