SQL 2012 AlwaysOn Availability Groups for SharePoint - Live360 Orlando 2012

  • 1,117 views
Uploaded on

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 …

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.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,117
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
55
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. What we will coverSQL 2012 AlwaysOn
  • 2. SQL 2012 AlwaysOnHype or Reality?
  • 3. History of AlwaysOn Availability GroupsBackground and Predecessor Technologies
  • 4. 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 SolutionAlwaysOn Availability Group - synchronous- Zero Seconds Yes 0-2commitAlwaysOn Availability Group - asynchronous- Seconds Minutes No 0-4commitAlwaysOn Failover Cluster Instance NA Minutes Yes NADatabase Mirroring - High-safety (sync + witness) Zero Seconds Yes NADatabase Mirroring - High-performance (async) Seconds Minutes No NALog Shipping Minutes Minutes No Not during -to-hours a restoreTraditional Backup, Copy, Restore Hours to Hours to No Not during days weeks a restore
  • 5. AlwaysOn Availability GroupsDesign Options
  • 6. AlwaysOn Availability GroupsRead-only Farms
  • 7. Design Options for SQL 2012Sample 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
  • 8. AlwaysOn Availability GroupsSynchronous vs. Asynchronous Database Support you CANNOT replicate databases synchronously unless you have 1Gb+ bandwidth and less than 10ms of latency!
  • 9. AlwaysOn Availability Groups for SharePoint Improving Data Tier High Availability and Disaster RecoveryCAVEAT
  • 10. AlwaysOn Availability GroupsVersion Requirements Enterprise Enterprise
  • 11. AlwaysOn Availability GroupsPrerequisites 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
  • 12. AlwaysOn Availability GroupsPrerequisites and Requirements – SQL Server
  • 13. AlwaysOn Availability GroupsCluster Witness and Voting Fundamentals • Automatic failover clustering requires servers to have the proper number of votes to ‘turn on’ a database copy. • There must always be a majority of votes to enable the node. • If a majority cannot be reached (for example, if there are only an even number of votes) the DBs will remain offline. • File Servers can act as File Share Witness (FSW) servers (additional votes.) • This avoids split-brain scenarios where multiple copies of a DB are online. • Be sure to give the Cluster Computer Account Full control to the FSW Share
  • 14. Creating AlwaysOn Availability GroupsStep 1: Create Windows Server Failover Cluster (WSFC)
  • 15. Creating AlwaysOn Availability GroupsStep 2: Prepare Nodes http://support.microsoft.com/kb/918992/
  • 16. Creating AlwaysOn Availability GroupsStep 2: Enable AlwaysOn on each SQL Node
  • 17. Creating AlwaysOn Availability GroupsStep 3: Create the Availability Group
  • 18. Creating AlwaysOn Availability GroupsStep 3: Create the Availability Group – Continued…
  • 19. Creating AlwaysOn Availability GroupsStep 3: Create the Availability Group – Continued…
  • 20. Creating AlwaysOn Availability GroupsStep 4: Create the Availability Group Listener
  • 21. Session SummarySQL 2012 AlwaysOn Availability Groups for SharePoint 2010
  • 22. Michael Noel Twitter: @MichaelTNoel www.cco.comSlides: slideshare.net/michaeltnoel