The document discusses implementing an always-on deployment for SharePoint. It covers definitions of business continuity, disaster recovery, high availability and recovery objectives. It also summarizes options for architectures using SQL AlwaysOn across multiple data centers for high availability and disaster recovery of SharePoint environments. Key aspects include synchronous or asynchronous data replication, testing plans and establishing service level agreements.

1. SharePoint Always-On Deployment
Mike Maadarani
SharePoint Architect
mike@maadarani.com
November 22rd, 2014

2. Thank you to all of our Sponsors!!

3. Remember to fill out your evaluation forms to win some great
prizes!
&
Join us for SharePint today!
Date & Time: Immediately after prizes
Location: Observatory Student Pub
Address: On Algonquin Campus
Parking: No need to move your car!*
Site: http://www.algonquinsa.com/ob.aspx
*Please drive responsibly! We are happy to call you a cab 

4. Bio..
Mike Maadarani
App Dev and Architecture for over 19 years (16 Years Microsoft, 3
Years with the “Other Guys”)
Business focused on Enterprise Content Management & Publishing
Sites
Technology focused on SharePoint, SQL Server and SharePoint
Integration
Architect, trainer, and presenter
mike@maadarani.com
www.maadarani.com/blog @mikemaadarani

5. Cloud
Agenda
SQL Always-ON
Applications Closing and Q&A
Definition
SharePoint High Availability
Disaster Recovery

6. Definition
Business Continuity
Encompasses a loosely defined set of planning, preparatory and
related activities which are intended to ensure that an organization's
critical business functions will either continue to operate
despite serious incidents or disasters that might otherwise have
interrupted them, or will be recovered to an operational state within a
reasonably short period.

7. Definition
Disaster Recovery
A disaster recovery plan (DRP) is a documented process or set of
procedures to recover and protect a business IT infrastructure in the
event of a disaster. Such plan, ordinarily documented in
written form, specifies procedures an organization is to follow in the
event of a disaster. The disaster could be natural, environmental or
man-made. Man-made disasters could be intentional (for example, an
act of a terrorist) or unintentional (that is, accidental, such as the
breakage of a man-made dam).

8. Definition
Disaster Recovery in reality

9. Solution?

11. The End!

12. The End!

13. Service Level Agreements
Availability % Downtime / Year Downtime / Month Downtime / Week
99% 3.65 days 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

14. Service Level Agreements
Availability % Downtime / Year Downtime / Month Downtime / Week
99% 3.65 days 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

15. Defining Requirements
Recovery Point Objective (RPO)
Acceptable amount of data loss measured in time
Recovery Time Objective (RTO)
Duration of time within which a business process must be restored after a disaster
RPO RTO
Example:
RPO of 1 hour
RTO of 3 hours

16. Stretched Farms – HA or DR
SharePoint Farm
< 1ms
Datacentre A Datacentre B

17. Business continuity inhibitors

18. Service Level Agreements
Availability % Downtime / Year Downtime / Month Downtime / Week
99% 3.65 days 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

19. On-premise Architecture Considerations
Applications
Data
Infrastructure
Storage
Network
Provider

20. SharePoint Architecture
DR Approach
SharePoint Cold Standby
SQL Hot Standby
(Always On)
VM Online Schedule
SQL 24x7 Always On
(only 1 member)
SharePoint + SQL 16hr/week - Patch
Maintenance,
Change Management
All Servers 40hrs/Half DR
Failover Test

21. What do I Sync?
SharePoint Configurations
Content Databases
Web Application Settings
Service Applications
Services
Custom Solutions
3rd Party tools

22. SharePoint DR

23. DR Deployment Process
Provision
Production
Farm
Validate
Production
Farm
Configure DR
Infrastructure
Setup SQL
Always-On
Provision DR
Farm
Validate DR
Monitoring &
Config Mgmt.
Test
SPRaaS
Service

24. Search Medium Farm Topology
Adm
Adm

25. Scalable Applications
Non-scalable Scalable

26. Scalable App Architecture

27. SQL/Data
SQL 1
FARM 1
SQL 2
FARM 2
SQL 3
Clustered Resources
Failover Cluster

28. RPO/RTO Options
Mirroring - Async
AlwaysOn - Async
Failover Clustering
Mirroring - Sync
Backup/Restore
Log Shipping
AlwaysOn - Sync
Zero Seconds Minutes Hours Days Weeks

29. Data Centers
Datacentre A Datacentre B
Provider 1 Provider 2

30. Infrastructure
Network
Active Directory
Network

31. Infrastructure
Network
Active Directory
Network
• X Power Supplies
• X fans
• X NICs
• Swappable HDD
• X Controllers
• X CPUs

32. Other Options
Network
Office Web
Applications
Farm
SharePoint
Farm
Directory
Network
Content & SA
Data

33. Cloud Options
SaaS
Consume the
Cloud
User Ready
O365
PaaS
Leverage the
Cloud
Developer Ready
Azure Roles
IaaS
Be the
Cloud
Operations Ready
Azure VM

34. 99.997%

35. Cloud Benefits
New
Secure
$$

36. Services
On-premise Infrastructure
(as a service)
Platform
(as a service)
Software
(as a service)

37. Session Objectives and Takeaways
3
Understand the concepts of Business
Continuity and the implications for
SharePoint
Differentiate between High Availability and
Disaster Recovery
Gain a deeper understanding of using SQL
Server AlwaysOn for implementing HA/DR
for SharePoint
Agree on an SLA
Invest in Software and Infrastructure
3rd Party Tools (Metalogix)
TEST TEST TEST

38. Fill out your Evals!
Q & A
Thank You / Merci
www.maadarani.com, mike@maadarani.com , @mikemaadarani
www.slideshare.net/maadarani