SQL 2012 AlwaysOn Availability Groups (AOAGs) for SharePoint Farms - Norcall SQL Intelligence Conference
•Télécharger en tant que PPTX, PDF•
1 j'aime•1,760 vues
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (10)
Similaire à SQL 2012 AlwaysOn Availability Groups (AOAGs) for SharePoint Farms - Norcall SQL Intelligence Conference
Similaire à SQL 2012 AlwaysOn Availability Groups (AOAGs) for SharePoint Farms - Norcall SQL Intelligence Conference (20)
Plus de Michael Noel
Plus de Michael Noel (20)
Dernier
Dernier (20)
SQL 2012 AlwaysOn Availability Groups (AOAGs) for SharePoint Farms - Norcall SQL Intelligence Conference
- 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
- 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. AlwaysOn Availability Groups Cluster 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. • Very important concept to understand for AOAG
- 15. Creating AlwaysOn Availability Groups Step 1: Create Windows Server Failover Cluster (WSFC)
- 16. Creating AlwaysOn Availability Groups Step 2: Prepare Nodes
- 17. Creating AlwaysOn Availability Groups Step 2: Enable AlwaysOn on each SQL Node
- 18. Creating AlwaysOn Availability Groups Step 3: Create the Availability Group
- 19. Creating AlwaysOn Availability Groups Step 3: Create the Availability Group – Continued…
- 20. Creating AlwaysOn Availability Groups Step 3: Create the Availability Group – Continued…
- 21. Creating AlwaysOn Availability Groups Step 4: Create the Availability Group Listener
- 23. Session Summary SQL 2012 AlwaysOn Availability Groups for SharePoint 2010
- 24. Michael Noel Twitter: @MichaelTNoel www.cco.com Slides: slideshare.net/michaeltnoel