This document provides an overview of SQL Server 2012 AlwaysOn Availability Groups. It begins with a history of AlwaysOn and compares it to other SQL high availability and disaster recovery solutions. Key features of AlwaysOn such as synchronous and asynchronous data replication, automatic failover, and readable secondary replicas are discussed. The document also covers design options, requirements, and steps for creating an AlwaysOn Availability Group. It concludes by promoting an upcoming SharePoint conference in Las Vegas.
6. History of AlwaysOn Availability Groups
Background and Predecessor Technologies
7. Comparison of AlwaysOn with other SQL HA
Greatly Improved HA and DR
High Availability and Disaster Potential Potential
Automatic Readable
Recovery Data Loss Recovery
Failover Secondaries
(RPO) Time (RTO)
SQL Server Solution
AlwaysOn Availability Group - synchronous- Zero Seconds Yes 0-2
commit
AlwaysOn Availability Group - asynchronous- Seconds Minutes No 0-4
commit
AlwaysOn Failover Cluster Instance NA Seconds Yes NA
-to-minutes
Database Mirroring - High-safety (sync + witness) Zero Seconds Yes NA
Database Mirroring - High-performance (async) Seconds Minutes No NA
Log Shipping Minutes Minutes No Not during
-to-hours a restore
Backup, Copy, Restore Hours Hours No Not during
-to-days a restore
13. AlwaysOn Availability Groups
Prerequisites and Requirements – Windows OS
http://support.microsoft.com/kb/976097
http://support.microsoft.com/kb/2494036
http://support.microsoft.com/kb/2531907
http://support.microsoft.com/kb/2616514
http://support.microsoft.com/kb/2654347
http://support.microsoft.com/kb/980915
http://support.microsoft.com/kb/2578113
http://support.microsoft.com/kb/2582281
25. REGISTER NOW!
www.sharepointconference.com
Join us in Las
Vegas for
SharePoint
Don’t miss this Engage with
the
Conference opportunity to community
2012!
join us in Las
Give yourself a Vegas at the
competitive edge Mandalay Bay Share
insights
and get the inside
scoop about
November 12-15
'SharePoint 15' while Learn about
learning how to what’s coming
next, from the
better use people who
built the
SharePoint 2010 product