Post on 14-Aug-2015
1
SharePoint High Availability or Disaster Recovery? That is the question.
Adam Levithan – Product ManagerPamela James Brooks – Solutions Engineer
April 2015
2
Enough About Us … What about you?
Poll
What infrastructure best describes your current environment?• Multiple versions of SharePoint (2007/2010/2013)• Geographically distributed on-premises Environment• Hybrid - SharePoint Online and SharePoint On-Premises• Office 365/ SharePoint Online Only
4
SharePoint High Availability or Disaster Recovery?
What If ?
I care about …
Disaster Recovery VS. High Availability
High Availability Demonstration
Key Considerations & Next Steps for Implementation
17
SharePoint Continuity Solutions Map
SeverityEnterprise-wide
DisasterDaily Events
Busi
ness
Impa
ct
MissionCritical
No Impact
Perf
orm
ance
Exp
ecta
tions
Fast
Slow
18
Remote BLOB
Storage
SharePoint Continuity Solutions Map
High Fidelity Backup & Granular Recovery
High Availability/ Warm Standby
OOTB Backup
Enterprise Backup
SeverityEnterprise-wide
DisasterDaily Events
Busi
ness
Impa
ct
MissionCritical
No Impact
Perf
orm
ance
Exp
ecta
tions
Fast
Slow
19
Disaster Recovery VS. High Availability
Disaster Recovery High Availability
RPO
RTO
Process
Servers
Access
Content
21
Definition: Recovery Time Objective (RTO)
The maximum time allowed for your environment to be restored after an outage or data loss
Example: 2 hour RTO means that data or farm must be restore within 2 hours of the system outage.
Time
UnacceptableBusiness
Consequences Begin
Disaster / Disruption
RTO
looks FORWARD
22
Definition: Recovery Point Objective (RPO)
Defined: the maximum tolerable time period in which data might be lost due to a server farm failure
Example: 4 hour RPO means that SharePoint must be backed at least every 4 hours
Time
RPOLast Sync
Next Sync
Data Loss RTO
Disaster / Disruption
looks BACKWARD
23
Disaster Recovery VS. High Availability
Disaster Recovery High Availability
RPO Typically Hours to days From minutes down to zero
RTO Typically Hours to days From minutes down to zero
Process
Servers
Access
Content
24
Definition: High Availability
A systematic approach / plan– Ensures that a data system, specifically, SharePoint and its content is continuously
operational and “live.”
Usually applied to the most critical content – Can never be down or “unavailable” and – Needs a safety net in the event of an outage
• Both planned or unplanned
25
Disaster Recovery VS. High Availability
Disaster Recovery High Availability
RPO Typically Hours to days From minutes down to zero
RTO Typically Hours to days From minutes down to zero
Process Manual / Involved Light to Automatic
Servers
Access
Content
26
Common Method to Architect Around the Problem – SQL Mirror & AlwaysOn
High Availability and Disaster RecoverySQL Server Solution
Potential Data Loss (RPO) Potential Recovery Time (RTO) Automatic
FailoverAdditional
Readable Copies
AlwaysOn Availability Groups - Synchronous (Dual-phase commit, no data loss, can’t operate across WAN)
None 5-7 Seconds Yes 0 - 2
AlwaysOn Availability Groups - Asynchronous (Latency tolerant, cross WAN option, potential for data loss)
Seconds Minutes No 0 - 4
AlwaysOn Failover Cluster Instance (FCI) - Traditional shared storage clustering
NA 30 Seconds to several minutes (depending on disk failover)
Yes N/A
Database Mirroring - High-safety (Synchronous) Zero 5-10 seconds Yes N/A
Database Mirroring - High-performance (Asynchronous) Seconds Manually initiated, can be a few minutes if automated
No N/A
SQL Log Shipping Minutes Manually initiated, can be a few minutes if automated, by
typically hours
No Not duringa restore
Traditional Backup and Restore Hours to Days
Typically multiple hours, days, or weeks
No Not duringa restore
27
Disaster Recovery VS. High Availability
Disaster Recovery High Availability
RPO Typically Hours to days From minutes down to zero
RTO Typically Hours to days From minutes down to zero
Process Manual / Involved Light to Automatic
Servers Homogenous setup Heterogeneous setup
Access Cold during recovery Hot / Live
Content
28
Analyst Perspective – Content Replication
Allows for SharePoint information to extend beyond a single geographic location
Information can be located logically closer to the end user
Creates a highly resilient, distributed environment that is easier to scale
Supports the needs of compliance, backup and archiving of SharePoint Information
Can reduce overall operational overhead
Frank Ohlhorst – SharePoint Pro
29
Disaster Recovery VS. High Availability
Disaster Recovery High Availability
RPO Typically Hours to days From minutes down to zero
RTO Typically Hours to days From minutes down to zero
Process Manual / Involved Light to Automatic
Servers Homogenous setup Heterogeneous setup
Access Cold during recovery Hot / Live
Content Must be identical Identical or Subset
34
High Availability DemonstrationMetalogix Replicator Demonstration
http://www.metalogix.com/Products/Replicator/Replicator-for-SharePoint.aspx Alevithan@metalogix.com
35
Key Considerations for Content Replication
Cost of a disruption
Amount of content that needs to be highly available
Collaboration/Mission Critical requirements – Always up-to-date content through active synchronization
Number of farms being connected, and their geographic distribution
Bandwidth required for replication
Conflict resolutions, fault-tolerance and fail-over
Migration/Upgrade path of SharePoint and third party tool
Preferred access to control
36
What to do next
Prioritize Content− Mission Criticality− Compliance/ Regulatory needs
Identify the initial effort to manage content− Database growth and user loads− Measure operational tasks required in current state− Identify bandwidth usage and latency
Perform the Business Cost Analysis− Describe the risk of NOT utilizing Replication− How will the Infrastructure be managed?
37
QuestionsGet More Information & Request a Custom Demonstration
http://www.metalogix.com/Products/Replicator/Replicator-for-SharePoint.aspx Alevithan@metalogix.com
@collabadam