SharePoint 2013 High Availability and Disaster Recovery with SQL Server Always On Availability Groups (HA and DR) - SharePoint Saturday Helsinki-Serge Luca (SharePoint MVP) et Isabelle Van Campenhoudt(SQ Server MVP); ShareQL, Belgium

1. SharePoint Saturday
Helsinki
Unbreakable SharePoint 2013
With SQL Server Always On
Isabelle Van Campenhoudt & Serge Luca

2. SharePoint Saturday Helsinki
Thank you to our sponsors!

3. ShareQL
3
Isabelle Van Campenhoudt
MVP SQL Server
TheSQLgrrrl.wordpress.com
Bruxelles
Serge Luca
MVP SharePoint
Sergeluca.wordpress.com
Bruxelles
ShareQL.com

4. Isabelle Van Campenhoudt
Isabelle Van
Campenhoud
t
SQL Server MVP, Bruxelles
Consultant, speaker, trainer, PASS V-Chapter Leader
Managing partner de www.ShareQL.com
SQL Server depuis 1999
Blog: http://thesqlgrrrl.wordpress.com/
ivc@ShareQL.com
@thesqlgrrrl
Isabelle
Van Campenhoudt
4
globalfrench.sqlpass.org

5. Serge Luca
Serge Luca
SharePoint MVP, Bruxelles
Consultant, speaker, trainer
Managing partner de www.ShareQL.com
SharePoint since 2001
Blog: http://sergeluca.wordpress.com/
sergeluca@ShareQL.com
@SergeLuca
Serge Luca

6. Business Continuity - Concepts
SharePoint 2013 Architecture and Business Continuity
SharePoint 2013 and Business Continuity
SQL Server and Always On Availability Groups
SharePoint 2013 and Always On Availability Groups
Conclusions – Q&A
Agenda

7. Business Continuity

8. Start from the business
Good management practices, start from the
business
• Don’t reinvent the wheel:
• ISO 22301
• Compatible with :
• ISO 9001 (quality)
• ISO 27001 (security)
• http://www.iso.org/iso/fr/news.htm?refid=Ref1602

9. IT Role
Prevent incidents
•Proactive Monitoring
•Staff organization
In case of incident
•HA (High Availability)
•DR (Disaster Recovery)

10. Terminology
Service Level Agreement
HA DR RPO RTO

11. Requirements
Recovery Point Objective (RPO)
How much data can we afford to loose ?
Recovery Time Objective (RTO)
How long can we afford to wait ?
RPO RTO
Example:
RTO 1 hour
RPO 3 hours
“I wait max 1 hour
I loose max 3 hours of data”

12. Service Level Agreement (SLA)
Contracted delivery time
Availability% Stop/Year Stop/Month Stop / Week
99% 3.65 hours 7.20 hours 1.68 hours
99.9% 8.76 hours 43.20 minutes 10.10 minutes
99.99% 52.56 minutes 4.32 minutes 1.01 minutes
99.999% 5.26 minutes 25.90 seconds 6.05 seconds
99.9999% 31.50 seconds 2.59 seconds 0.61 seconds

13. RPO/RTO versus Cost
RPO/RTO Cost
NH

14. HA DR
HA DR

15. Architecture
SharePoint 2013

16. A SharePoint farm is not alone…
Office Web
App farm
Wokflow
Manager
farm
SharePoint 2013
farm

17. SharePoint Farm
Site
collection
Sites
Listes
Web
applications
(= IIS web
sites)
Farm
Content
database
Configuration
Database
Service
Application
Service
Databases

18. SharePoint and
Business Continuity

19. Server redundancy
• SharePoint, Office Web
App, Workflows, SQL
Services redundancy
• Services can be started
on several machines
• Different roles : search
Architecture H-A (High Availability)

20. SharePoint patching and downtime
patches
preparation
Patching machine 1 machine 1 patched
Patching machine 2 Psconfig on machine 1 Psconfig on machine 2
How can we patch
without
downtime ?

21. SharePoint machines active in 2 data centers
Unsupported unless
• latency between web front ends et SQL Server< 1 ms
• 10 minutes
• 99.9 %
• Network > 1 Gbits /sec
DANGER : Stretched Farm

22. Ok only if the SharePoint farm is
Stopped (physically stop VMs and take DB backups)
Every machine has a config cache
Snapshot is not atomic
Danger : VMs Snaphots

23. SQL Server and Always On
Availability Groups (AOAG)

24. SQL toolbox
Backup, Copy,
Restore
Log Shipping
Database
Mirroring
Always On
Failover Cluster
Instance
Always On
Availability
Groups (AOAG)

25. High Availability and Disaster Recovery
Potential
Data Loss
(RPO)
Potential
Recovery
Time (RTO)
Automatic
Failover
Readable
Secondaries
Backup, Copy, Restore hours
hours -to-
days No
Not during a
restore
Log Shipping Minutes
Minutes-to-
hours No
Not during a
restore
Database Mirroring - High-safety (sync + witness) Zero seconds Yes NA
Database Mirroring - High-performance (async) seconds Minutes No NA
Always On Failover Cluster Instance NA
seconds to
minutes Yes NA
Always On Availability Groups - synchronous-
commit Zero seconds Yes 0 – 3
Always On Availability Groups - asynchronous-
commit seconds Minutes No 0 - 8
Comparison Always On and other SQL Servers HA & DR

27. SQL Server AlwaysOn Availability Groups
Architecture

28. Pitfalls for Availability Groups
Installation
• File location
• Security
• AD permissions
• Network/DNS/MultiSubnet
Operations
• Backups & Logs
• Logins synchronization
• Patching

29. ALWAYS ON AVAILABILITY GROUPS

30. SharePoint and Always On
Availability Groups

31. SharePoint and Always On Availability Groups

32. • HA : nodes update in sync mode
• DR : nodes update in async mode
2
situations :
• Secondary nodes can be read (licence!)
• And used for backups..
• Switch very fast
• Switch logic based on quorum in the
Cluster
Other
benefits :

33. Always On Availability & SharePoint
SQL 1
FARM 1
SQL 2
High
Availabilty
Synchronous

34. HA-Always On Availability Groups &
SharePoint
SQL 1
FARM 1
SQL 2
Synchronous
High
Availabilty

35. • SharePoint 2013 with SP1 and CU April 2014
• SQL alias & pointing to a SQL node
• Setup the farm /connected to alias (SPAutoInstaller)
Install the SharePoint farm
• Recovery mode to “full” for databases to be sync
• Usage database: NO
• SharePoint databases Full Backup
• !!! In Test take log backups
Configure SharePoint
SharePoint for Always On AG
• Create Windows Cluster and add every SQL Node
• Create 1 or n Always On AG & Add SharePoint DB
• Create the listener
• Copy SP logins & permissions and other server objects on every node
Configure SQL Server Cluster
& Always On
• Test failover with SharePointTest
How to HA with AOAG
Everything can
easily be scripted !

36. Nice to have: several Availability Groups
• 1 for content databases
• 1 for search databases
• 1 for other service
databases
• 1 for other SharePoint
(Config, Central Admin)
several
availability
groups

37. Database Support – Sync
Commit
Database Supported
Admin Content Yes
App Management Yes
BDC Yes
Config Yes
Content Yes
Managed Metadata Yes
PerformancePoint Yes
PowerPivot Not Tested
Project Yes
Search Analytic Reporting Yes
Search Admin Yes
Database Supported
Search Crawl Yes
Search Links Yes
Secure Store Yes
State Service Yes
Subscription Settings Yes
Translation Services Yes
UPA Profile Yes
UPA Social Yes
UPA Sync Yes
Usage(=loggingDB) Yes – NR
Word Automation Yes
WE

38. SP HIGH AVAILABILITY

39. DR with Always On Availability Groups &
SharePoint
SQL 1
FARM 1
SQL 2
FARM 2
SQL 3
Asynchronous
Disaster
Recovery
Synchronous

40. Database Support – Async Commit
Database Supported
Admin Content No
App Management Yes
BDC Yes
Config No
Content Yes
Managed Metadata Yes
PerformancePoint Yes
PowerPivot Not Tested*
Project Yes
Search Analytic Reporting No
Search Admin No
Database Supported
Search Crawl No
Search Links No
Secure Store Yes
State Service No
Subscription Settings Yes
Translation Services Yes
UPA Profile Yes
UPA Social Yes
UPA Sync No
Usage Yes – NR
Word Automation Yes
WE

41. Install Farm number 1
• Connect it on AG
listener or on Node 1
Install Farm number 2
• Databases:
configuration,
central admin,
search, user profile
sync on node 2
• Other databases
(content and services)
come from farm 1
How to setup DR with 2 farms

42. Backup/Restore of the search
Service application
Impact on SLA !
• O365 search SLA = 1 week 
Search and DR

43. SHAREPOINT DISASTER RECOVERY

44. Conclusions

45. Conclusions
Define SLAs with the business
Major Role of SQL Server AOAG in HA/DR
HA = 1 SP farm SP, DR = 2 SP farms
• Search limitation !!!
SP farm + Workflow farm + Office Web App farm

46. Kiitos, Merci !
ivc@shareql.com
@thesqlgrrrl
sergeluca@shareql.com
@sergeluca