SharePoint Out of the Box Content Recovery, Disaster Recovery, and High Availability OptionsJavierBarrera.firstname.lastname@example.org@jtbarrera(210) 312-5336The best way to reach me is via email.
General into over topicWhat are we talking about….This session is focused on introducing SharePoint Out of the Box Content Recovery, Disaster Recovery, and High Availability Options. This will be an introductory session. Please ask any questions as needed. I will be happy to answer your questions and provide real world examples.
I will talk briefly why I’m so interested in this topic.I’m a SharePoint engineer whose main focus is architecture and infrastructure. I have multiple customers each with unique needs and business requirements. I’ll talk about my frustrations and solutions.
Here I will address the general confusion around this product and why we are here.
Continuity – This defines simple recovery of items without major disruption of services (trash can)High Availability – This is the ability for your farm to partially fail but still provide services (resiliency)Disaster Recovery – This is the category of a total farm failure and process around recovering that farm
Lack of SharePoint maturity. It doesn’t get any better in SharePoint 2013. Where we are at SharePoint 2010 work-aroundsWhat we want: we want to be able to be confident in our systems for such an important systemCompare to mature exchange or Lync
Recovery Level Object (RLO) - This defines to what level you wish to back and recover SharePoint objects. (sites, sub-sites, lists, list items)Recovery Point Objective (RPO) – This defines how often you back up and can recovery point. (weekly, daily, hourly)Recovery Time Objective (RTO) – This is the amount of time it can take to get to the recovery point objective. Standardized Operating Procedure (SOP) - A standardized and documents process of steps in times of recovery
The boring cycle chart. Boring but important and easily dismissed as cliché As depicted it is continuous cycle of planning-testing-assessing-replaning
Out first basic and easiest toolFirst Stage: User recoverable, count to quota, time Second Stage: site collection admin, time limit (default 30), no storage limit, unless quota
To manage size use quotasParticularly important in publishing sitesBetter handling of storage and version in SharePoint 2013Don’t version Access or PowerPoint files
Powershell or GUISharePoint DesignerBackup & restoreExport & ImportConsider size import/export -> backup-site -> SQL -> SQL + Diffs
restore or copy content, such as sites, site collections, lists, or document libraries, from a content database without having to attach the content database to the farm.PowershellGUIPre SP1 cautionMemory considerations
This represents HA in a single data center and available SQL options
Taking it a step further down the chain to HA for entire farm. Be careful of replication options at this level.
Stand by Data Center
 Warm or Hot Farm config
 Logically identical
 Not all Service Application
databases can be copied
 Most Content databases can
 What about the end-user?
 3rd party product…
What Can’t I Replicate?
Parts of User Profile Service
3rd party service databases
SQL 2012 AlawaysOn?
 SQL 2012 Enterprise Only
 Performance Hit
 Does not overcome most SharePoint weaknesses
 No Shared Storage requirements
 Replication can happen at 1-1 or 1-many
 Replication can happen as a set of databases
Leads to Success!
 SharePoint 2010 Products backup and recovery planning
 Plan for business continuity management