Webinar Critical SQL Server Databases: Provide HA with SQL Server Failover Clustering and Cluster Shared Volumes
Edwin Sarmiento Microsoft MVP/Microsoft Certified Master: http://www.edwinmsarmiento.com edwin@edwinmsarmiento.com @EdwinMSarmiento http://ca.linkedin.com/in/edwinmsa rmiento
high availability
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
high availability is NOT the same as UPTIME
Just because something is UP doesn t mean it s available available
high availability Recovery Time Objective (RTO) When is my application coming back?
high ZERO downtime
downtime 90 (one nine ) 36.5 days per year 72 hours per month % availability 16.8 hours per week
downtime 99 (two nines ) 3.65 days per year 7.2 hours per month % availability 1.68 hours per week
downtime 99.9 (three nines ) 8.76 hours per year 43.8 minutes per month % availability 10.1 minutes per week
downtime 99.99 % availability (four nines ) 52.56 per year minutes 4.32 minutes per month 1.01 minutes per week
downtime 99.999 (five nines ) 5.26 minutes per year 25.9 seconds per month % availability 6.05 seconds per week
downtime 99.999 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
Cost 70000 60000 50000 40000 Availability/RTO versus Total Cost of Ownership 30000 20000 10000 0 1 2 3 4 5 6 7 8 9 10 11 Time
high ZERO downtime
high availability features
https://msdn.microsoft.com/en-us/library/cc645993.aspx#high_availability
ALWAYSON AVAILABILITY GROUPS
*DATABASE (group) protection ALWAYSON AVAILABILITY GROUPS introduced in SQL Server 2012
*DATABASE (group) protection ALWAYSON AVAILABILITY GROUPS can either be an HA and/or DR solution
ALWAYSON AVAILABILITY GROUPS combination of DATABASE MIRRORING & FAILOVER CLUSTERING
*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
challenge Availability Group requires SQL Server Enterprise Edition
FAILOVER CLUSTERING
FAILOVER CLUSTERING can either be an HA and/or DR solution *INSTANCE protection
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
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
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 2012 + Windows Server Failover Cluster
Windows Server Failover Cluster SQL Server let s look at failover in the context of the storage
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
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
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
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
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
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
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
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
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
What does StarWind Virtual SAN change? StarWind Virtual SAN turns local storage into fault tolerant CSV for the local SQL cluster
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
Configure SQL Server 2014 Failover Clustered Instances to use Cluster Shared Volumes demo
Edwin Sarmiento Microsoft MVP/Microsoft Certified Master: http://www.edwinmsarmiento.com edwin@edwinmsarmiento.com @EdwinMSarmiento http://ca.linkedin.com/in/edwinmsa rmiento