The release of SQL Server 2012 provides for unprecedented high availability and disaster recovery options for SharePoint farms in the form of AlwaysOn Availability Groups, the newest form of Database Mirroring. Using this new technology, SharePoint architects can provide for near-instant failover at the data tier, without the risk of any data loss. This technology, which will be demonstrated live, completely changes the data tier design options for SharePoint and revolutionizes high availability options for a farm. This session covers in step by step detail the exact configuration required to enable this functionality for a SharePoint 2010 or SharePoint 2013 farm, based on the Best Practices, tips and tricks, and real-world experience of the presenter in deploying this technology in production. • Understand the differences between SQL AlwaysOn options, and determine the requirements to deploy the technologies • Examine how SQL Server 2012 AlwaysOn Availability Groups can provide aggressive Service Level Agreements (SLAs) with a Recovery Point Objective (RPO) of zero and a Recovery Time Objective (RTO) of a few seconds. • See the exact steps required to enable SQL Server 2012 AlwaysOn Availability Groups for a SharePoint 2010 or SharePoint 2013 environment

3. What we will cover
SQL 2012 AlwaysOn

4. SQL 2012 AlwaysOn
Hype or Reality?

5. History of AlwaysOn Availability Groups
Background and Predecessor Technologies

6. 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

7. AlwaysOn Availability Groups
Design Options

8. AlwaysOn Availability Groups
Read-only Farms

9. Design Options for SQL 2012
Sample Design
• Two AGs
• Content AG
with four
replicas –
Synch and
Asynch
• Service
App/Farm DBs
on separate
AG, 2 Synch
copies only
• Read-only
farm in remote
office attached
to content DB
copy
• DR farm in
remote DC on
standby to
connect to
content DB
copy

10. AlwaysOn Availability Groups for SharePoint
Improving Data Tier High Availability and Disaster Recovery
CAVEAT

11. AlwaysOn Availability Groups
Version Requirements
Enterprise
Enterprise

12. 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

13. AlwaysOn Availability Groups
Prerequisites and Requirements – SQL Server

14. Creating AlwaysOn Availability Groups
Step 1: Create Windows Server Failover Cluster (WSFC)

15. Creating AlwaysOn Availability Groups
Step 2: Prepare Nodes

16. Creating AlwaysOn Availability Groups
Step 2: Enable AlwaysOn on each SQL Node

17. Creating AlwaysOn Availability Groups
Step 3: Create the Availability Group

18. Creating AlwaysOn Availability Groups
Step 3: Create the Availability Group – Continued…

19. Creating AlwaysOn Availability Groups
Step 3: Create the Availability Group – Continued…

20. Creating AlwaysOn Availability Groups
Step 4: Create the Availability Group Listener

22. Session Summary
SQL 2012 AlwaysOn Availability Groups for SharePoint 2010

23. Michael Noel
Twitter: @MichaelTNoel
www.cco.com
Slides: slideshare.net/michaeltnoel
Travel Blog:
SharingTheGlobe.com