Download as PDF, PPTX
Uploaded byStarWind Software
Critical SQL Server Databases: Provide HA with SQL Server Failover Clustering and Cluster Shared Volumes
The document discusses high availability (HA) in SQL Server databases, emphasizing the significance of continuous uptime versus mere operational status. It covers various availability percentages and their corresponding downtime, highlighting solutions like AlwaysOn Availability Groups and Failover Clustering to enhance resilience. Additionally, it introduces Starwind Virtual SAN as a cost-effective way to create fault-tolerant Cluster Shared Volumes by leveraging local storage.
More Related Content
Similar to Critical SQL Server Databases: Provide HA with SQL Server Failover Clustering and Cluster Shared Volumes
Critical SQL Server Databases: Provide HA with SQL Server Failover Clustering and Cluster Shared Volumes
- 1. Webinar Critical SQL ServerDatabases: Provide HA with SQL Server Failover Clustering and Cluster Shared Volumes
- 2.
- 4.
- 5. high availability characteristic of asystem that is full y oper ational for a long period of time
- 6. high availability is NOT thesame as UPTIME
- 7. Just because something is UP doesn’tmean it’s available UP available
- 8. Recovery Time Objective (RTO) high availability Whenis my application coming back?
- 9.
- 10. (one “nine”) % availability 90 36.5 days peryear 72 hours per month 16.8 hours per week downtime
- 11. (two “nines”) % availability 99 3.65 days peryear 7.2 hours per month 1.68 hours per week downtime
- 12. (three “nines”) % availability 99.9 8.76 hours peryear 43.8 minutes per month 10.1 minutes per week downtime
- 13. (four “nines”) % availability 99.99 52.56 minutesper year 4.32minutes per month 1.01 minutes per week downtime
- 14. (five “nines”) % availability 99.999 5.26 minutes peryear 25.9 seconds per month 6.05 seconds per week downtime
- 15. (five “nines”) % availability 99.999 5.26 minutes peryear 25.9 seconds per month 6.05 seconds per week downtime How long does it take to restart S Q L S e r ver
- 16. 0 10000 20000 30000 40000 50000 60000 70000 1 2 34 5 6 7 8 9 10 11 Cost Time Availability/RTO versus Total Cost of Ownership
- 17.
- 18.
- 19.
- 20.
- 21. introduced in SQLServer 2012 ALWAYSON AVAILABILITY GROUPS *DATABASE (group) protection
- 22. can either bean HA and/or DR solution ALWAYSON AVAILABILITY GROUPS *DATABASE (group) protection
- 23. combination of DATABASE MIRRORING & FAILOVERCLUSTERING ALWAYSON AVAILABILITY GROUPS
- 24. SQL Server log data SQLServer log data Secondary ReplicaPrimary Replica SQL Server log data Secondary Repli *maximum of EIGHT replicas Windows Server Failover Cluster Database Mirroring
- 25. challenge Availability Group SQL Server EnterpriseEdition requires
- 26.
- 27. *INSTANCE protection FAILOVER CLUSTERING caneither be an HA and/or DR solution
- 28. log data failover clustering how itworks Windows Server Failover Cluster SQL Server 2-node cluster t r a d i t i o n a l
- 29. failover clustering how it works WindowsServer Failover Cluster SQL Server Application 2-node cluster t r a d i t i o n a l log data
- 30. Windows Server FailoverCluster shared disks containing an NTFS or ReFS volume that is made accessible for read and write operations by all nodes of WSFC cluster shared volumes* we will only focus on Windows Server 2012 + SQL Server
- 31. Windows Server FailoverCluster failover let’s look at in the context of the storage SQL Server
- 32. Windows Server FailoverCluster the storage is owned by I/O workload only goes thru that single path to the storage onlyoneclusternode atatime SQL Server
- 33. Windows Server FailoverCluster SQL Server AD/DNS during failover, the storage gets “logically” dismounted from the failed node and remounted on the new active/primary node
- 34. Windows Server FailoverCluster SQL Server AD/DNS 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. SQL Server Windows ServerFailover 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 FailoverCluster SQL Server with CSV, no need to remount storage on new active/primary node after failover this reduces downtime, increases resiliency and reliability SQL Server
- 37. Windows Server FailoverCluster with CSV, no more 23 drive letter limitations this means you no longer have to memorize the alphabet in terms of failover cluster drives SQL ServerSQL Server
- 38. Windows Server FailoverCluster with CSV, the concept of *this means that SQL Server failover clustered instances no longer has a direct dependency on the shared drive to come online exclusiveownership ofstorage is redefined SQL ServerSQL Server
- 39. failover clustering how it works WindowsServer Failover Cluster 2-node cluster t r a d i t i o n a l Application *can be implemented with SQL Server Standard Edition log data SQL Server
- 40. failover clustering how it works WindowsServer Failover Cluster 2-node cluster t r a d i t i o n a l Application *can be implemented with SQL Server Standard Edition log data log data HA SQL Server
- 41. What does StarWindVirtual SAN change? StarWind Virtual SAN turns local storage into fault tolerant CSV for the local SQL cluster
- 42. •Deployment price isreduced ~3 times •Maximized performance because of short IO path •Disk, RAM, and Flash FT without Enterprise SQL licensing Benefits compared to native clustering
- 43. demo Configure SQL Server2014 Failover Clustered Instances to use Cluster Shared Volumes
- 44.