sharepoint high availability & disaster recovery
DESCRIPTION
TRANSCRIPT
![Page 1: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/1.jpg)
high availability & disaster recovery for sharepointplanning & technology thomas vochten
13.03.2012
![Page 2: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/2.jpg)
about me
Thomas Vochten
@thomasvochtenthomasvochten.comlinkedin.com/in/thomasvochten
consultantplatform architectlousy developeraccidental dba
SharePoint
SQL Server
![Page 3: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/3.jpg)
#sphelp to the rescuehttps://twitter.com/search/%23sphelp
![Page 4: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/4.jpg)
setting the sceneha & dr overview
![Page 5: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/5.jpg)
high availability & disaster recoverycritical factor in any SharePoint deployment
however…
false expectations
fuzzy requirements
technicalmisconceptions
project failure
![Page 6: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/6.jpg)
high availabilityprotecting against component failures
• server hardware• operating system• service applications• application pools• custom development• …
![Page 7: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/7.jpg)
number of nines
3 days, 15 hours
• often an important part of a service level agreement (SLA)• usually only unplanned downtime
8 hours, 45 mins
52 mins, 34 secs5 mins, 15 secs
99%
99,9%
99,99%
99,999%
downtime per year
![Page 8: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/8.jpg)
disaster recoveryprotecting against catastrophes
• network outages• storage problems• power problems• loss of datacenters• …
![Page 9: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/9.jpg)
protect yourself
systems
components
dataoperations & procedures
build redundancy into the architecture
infrastructure
![Page 10: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/10.jpg)
the bigger pictureplanning for ha & dr
![Page 11: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/11.jpg)
it’s all about the business• involve all stakeholders when planning• don’t neglect the business impact• analyze data & systems• consider non-technical elements
business continuity planning
![Page 12: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/12.jpg)
key concepts of bcp• Risk assessment• Business Impact Analysis• Business Continuity Plan• Disaster Recovery Plan
![Page 13: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/13.jpg)
requirementsarchitecting a solution
![Page 14: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/14.jpg)
key parametersRecovery Time Objective (RTO)When will my system be available again?
Recovery Point Objective (RPO)How much data can I afford to lose?
Recovery Level Objective (RLO)To what level am I able to restore?
![Page 15: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/15.jpg)
time
RPO RTO
last backup at 20:00 full recovery at 12:00outage at 08:00
12h 4h
![Page 16: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/16.jpg)
reality check• What are acceptable RTO & RPO times?
• Is RTO and RPO 0 possible at all?• What about the costs?
time
RPO RTO
last backup at 07:55 full recovery at 08:15
outage at 08:00
5m 15m
![Page 17: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/17.jpg)
context is kingpitfalls when designing a SharePoint HA/DR solution
• enterprise infrastructure• technical skills• operational readiness• backup/restore• documentation• dependencies on other systems• 3d party tools• …
![Page 18: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/18.jpg)
additional considerationsestablish recovery targets
• What should be restored and what not?• What can be restored and what not?• Is some data more important than other?• How must the restored system behave?• Balance costs & risks when designing a solution
![Page 19: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/19.jpg)
the most crucial step• Test, test, test!
![Page 20: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/20.jpg)
technical solutionsSharePoint & SQL Server
![Page 21: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/21.jpg)
SharePoint optionshow can you make SharePoint highly available?
• adding servers for redundancy• splitting services across servers• using load balancing techniques• highly available SQL Server
![Page 22: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/22.jpg)
load balancing SharePoint
APP2service instance
APP1service instance
WEB2IIS
WEB1IIS
Web Requests
Service Apps
WEBnIIS
APPnservice instance
![Page 23: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/23.jpg)
service applicationshow to distribute service applications throughout your farm?
SharePoint takes care of the load balancing for you
![Page 24: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/24.jpg)
important considerations• user profile synchronization service only on 1 server• search service application can be made fully
redundant now
what about disaster recovery?
![Page 25: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/25.jpg)
SharePoint disaster protectionwhat are your options?
rebuild
cold standby
warm standby
hot standby
stretched farm
![Page 26: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/26.jpg)
rebuild farm
RTO
RPO
documentscript
• never simply dismiss this option• serious drawbacks however• backup/restore data• documentation is essential• script your install
?
![Page 27: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/27.jpg)
standby farms
cold standby
hotstandby
warmstandby
RTOhrs/days
RTOhrs/mins
RTOmins/secs RPO config!?
![Page 28: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/28.jpg)
warm / hot standby farms• completely separate farm• near identical configuration• same customizations• separate datastores• involves some kind of data
replication• replicating service app data has
its limits• manual failover & client
redirection
![Page 29: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/29.jpg)
service applicationsthese don’t support copying to another farm
configcentral admin bcs
search admin
search crawl
search property
user profile
![Page 30: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/30.jpg)
stretched farma special case…a lot of dependencies…some complexity involved…
major design constraints• network throughput• network latency• redundant access infrastructure• data replication
![Page 31: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/31.jpg)
SQL Server
![Page 32: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/32.jpg)
clusteringtwo flavors
• high availability• same datacenter• 2 or more nodes• shared storage• automatic failover• SharePoint is unaware
classic cluster
• high availability or disaster recovery• multiple datacenters• 2 or more nodes• no shared storage• automatic failover• SharePoint is unaware• data replication needed
geo cluster
![Page 33: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/33.jpg)
clustering summary
RPOdepends
RTO secs/mins
RLOfarm
how does it satisfy requirements?
failoverauto
![Page 34: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/34.jpg)
mirroring
essentials• high availability scenarios• no shared storage• SharePoint is aware !
nice to know• full recovery model• configured per database• only one secondary possible• secondary cannot be accessed• automatic failover possible• network constraints• sync or async
![Page 35: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/35.jpg)
native mirroring support
PowerShell
$db = Get-SPDatabase [UglyGuidGoesHere]
$db.AddFailoverServiceInstance(“servername”)
$db.Update()
User Interface
![Page 36: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/36.jpg)
mirroring summarysynchronous mirroring
asynchronous mirroring
RPO0
RTOsecs
RLOdepends
RPOseconds
RTOmins
RLOdepends
failoverauto
failovermanual
![Page 37: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/37.jpg)
log shipping
essentials• disaster recovery scenarios• no shared storage• backup/restore based
nice to know• full recovery model• configured per database• multiple secondary's possible• secondary can be read from• no automatic failover possible• rpo will generally not be 0
![Page 38: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/38.jpg)
log shipping summaryhow does it satisfy requirements?
RPOmins
RTOmins/hrs
RLOdepends
failovermanual
![Page 39: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/39.jpg)
SQL 2012 Availability Group
essentials• clustering & mirroring evolved• at the instance level• no shared storage• for ha & dr• simple configuration
nice to know• automatic failover across single or multiple datacenters• multiple databases fail over together• no need for aliases or AddFailoverServiceInstance in SharePoint• multiple (readable) secondaries possible• full recovery model• RBS support
the newest kid on the block
![Page 40: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/40.jpg)
SQL 2012 Availability Group
![Page 41: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/41.jpg)
SQL 2012 Availability Group summaryhow does it satisfy requirements?
RPO0
RTOsecs
RLOfarm
failoverauto HA & DR
![Page 42: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/42.jpg)
Putting it all together
![Page 43: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/43.jpg)
single farm / one datacenter• multiple web servers with load balancing• multiple application servers• clustering or mirroring for ha or dr• consider SQL 2012 availability groups!
![Page 44: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/44.jpg)
single farm / two datacenters• fully redundant network infrastructure• <1ms latency between datacenters• load balancing across datacenters• multiple web servers• multiple application servers• mirroring or geo cluster with data replication for ha &
dr• consider SQL 2012 availability groups!
![Page 45: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/45.jpg)
two farms / two datacenters• fully redundant network infrastructure• log shipping between data centers for dr• manual failover• manual client redirect (network routing, dns)• sometimes DR farm is read-only• warm / hot standby• consider SQL 2012 availability groups!
![Page 46: SharePoint High Availability & Disaster Recovery](https://reader031.vdocuments.net/reader031/viewer/2022020101/54803963b4af9f33698b4a94/html5/thumbnails/46.jpg)
questionsthank you for your attendance
@thomasvochten