1. Always On Multi-Site Patterns

2. About Me
John Q. Martin Product Manager for SentryOne Microsoft Data Platform MVP Over a decade of experience with SQL Server as a Dev, DBA and BI Dev. Most recently working as a Premier Field Engineer with Microsoft UK. Contact Info Twitter Blog : LinkedIn :

3. The One Platform for Physical, Virtual, and Cloud Performance.
SentryOne™ empowers Microsoft data professionals to monitor, diagnose, and optimize performance across physical, virtual, and cloud resources. The SentryOne platform delivers seamless integration for all of our solutions, enabling users to determine the true cause of performance issues, and reduce consumption and infrastructure costs.

4. The One Platform for Physical, Virtual, and Cloud Performance.
Free Resources
The One Platform for Physical, Virtual, and Cloud Performance.
Free e-books
In these books, you will find useful, hand-picked articles that will help give insight into some of your most vexing performance problems. These articles were written by several of the SQL Server industry's leading experts, including Aaron Bertrand, Paul White, Paul Randal, Jonathan Kehayias, Erin Stellato, Glenn Berry, and Joe Sack.
Websites SQLPerformance.com provides innovative and practical solutions for improving SQL Server performance. Answers.SQLPerformance.com is a question and answers site where you can upload query plans directly from Plan Explorer and have questions answered from execution plan analysis expert Paul White, among others. SQLSentry.TV offers an inside look into the world of SentryOne with videos on query tuning and product demos. Blogs.SentryOne.com is where you can find all of our team members’ blogs as well as important information about the latest updates to SentryOne software, SQL Server and server performance issues.

5. What is Always On?
FCI
Availability Groups

6. High Availability Disaster Recovery Definitions
Highly Available systems are comprised of systems configured to maintain service availability in the event of hardware failure on the primary site, highly available systems should result in less than five minutes of downtime when an event occurs and should involve no manual intervention. Data systems should be fully consistent and have no data loss other than that which was in-flight at the time of the event that caused the failover.
Disaster Recovery
Disaster Recovery systems are comprised of elements that can be brought online in the event of an issue to the main business site that results in the inability to perform business operations. It is anticipated that in the event of a Disaster situation the DR process will be enacted after a decision by the senior management of the business. In the event that the Disaster process is activated, the Disaster Recovery process should bring the platform online and ready for business transactions in no more than six hours with no more than fifteen minutes of data loss to the business.

7. Why Multi-Site?
Out of Order Image :

8. Multi-Site Considerations
Latency
Storage
Network connectivity
Operating system and software featrues

9. Failover Cluster Instances [FCI]
Region : UK South
FSW
Site 1
Site n.
WSFC
Storage Synchronisation

10. Availability Groups [AG]
Region : UK South
Multi-Site : High Availability
FSW
Region : West Europe
Region : North Europe
Windows Server Failover Cluster
[Asynchronous]
[Synchronous]
[Synchronous]
Replica : Primary
Replica : Secondary
Replica : Secondary
Replica : Secondary

11. Availability Groups [AG]
Region : UK South
Multi-Site : High Availability
FSW
Cloud Witness
Region : West Europe
Region : North Europe
Windows Server Failover Cluster
[Asynchronous]
[Synchronous]
[Synchronous]
Replica : Primary
Replica : Secondary
Replica : Secondary
Replica : Secondary

12. Availability Groups [AG]
Region : UK South
Multi-Site : High Availability
FSW
Region : West Europe
Region : North Europe
Windows Server Failover Cluster
[Asynchronous]
[Synchronous]
[Synchronous]
Replica : Primary
Replica : Secondary
Replica : Secondary
Replica : Secondary

13. Availability Groups [AG]
Region : UK South
Multi-Site : High Availability
FSW
Cloud Witness
Region : West Europe
Region : North Europe
Windows Server Failover Cluster
[Asynchronous]
[Synchronous]
[Synchronous]
Replica : Primary
Replica : Secondary
Replica : Secondary
Replica : Secondary

14. Availability Groups [AG]
Multi-Site : Disaster Recovery
Region : West Europe
Region : North Europe
FSW
Windows Server Failover Cluster
[Asynchronous]
Replica : Primary
Replica : Secondary
Replica : Secondary
Replica : Secondary
Replica : Secondary

15. Multi-Site : Stretch Clusters
Cluster Settings
CrossSubnetDelay
CrossSubnetThreshold
Allow for greater latency and unreliable link between sites.
Controls the IP Addresses that will be registered in DNS & the Time To Live (TTL).
Cluster Settings
RegisterAllProvidersIP
HostRecordTTL
Affects whether a node can participate in forming quorum.
Cluster Settings
NodeWeight

16. Availability Groups [AG]
Multi-Site : Disaster Recovery
Distributed Availability Group [Distributed AG]
Region : West Europe
Region : North Europe
FSW
FSW
Windows Server Failover Cluster
Windows Server Failover Cluster
[Asynchronous]
Replica : Primary
Replica : Primary
Replica : Secondary
Replica : Secondary
Replica : Secondary
Replica : Secondary

17. Azure Availability Configurations
Devil in the detail
Availability SLA requirements
Single or multiple machines, depending on storage
Allocates VMs to Fault Domains and Upgrade Domains
Who’s fault is it?
Use Availability Sets
GROUP BY
Resource Groups
Regions
Resource Groups are global for logical grouping of services

18. Identify multi-site requirement
Summary
Identify multi-site requirement
High Availability Or Disaster Recovery
Recovery Point/Time Objectives
Be aware of latency impact
Log synchronization
Storage synchronization
Failover Cluster Services configuration
Service Dependencies