SharePoint Business Continuity Management with SQL Server Always OnNeil HodgkinsonSenior Program ManagerMicrosoft CXP CAT

SPc343

Neil HodgkinsonPre-MicrosoftProcess Chemist (Drugs, Poisons and Explosives)

CSC SharePoint Specialist – 5 Years

Microsoft (2005-)SharePoint PFE - 5 Years

SharePoint Service Engineering O365 - 3 Years

Office 365 CXP CAT - Current

MCSM SharePoint Instructor Team

ContactEmail – neil.hodgkinson@microsoft.com

Twitter - @nellymo

Session Objectives And TakeawaysUnderstand the concepts of Business Continuity and the implications for SharePointDifferentiate between High Availability and Disaster Recovery Gain a deeper understanding of using SQL Server AlwaysOn for implementing HA/DR for SharePoint

AgendaDefinitionsSQL Server AlwaysOn OverviewSharePoint High AvailabilitySharePoint Disaster RecoveryRecent Support Changes

Definitions

Business Continuity Management“An organisation wide discipline and a complete set of processes that identifies potential impacts which threaten an organisation. It provides a capability for an effective response that safeguards the interests of its major stakeholders and reputation.”

Consists of High Availability and Disaster RecoveryIndustry Standard ISO22301

High Availability“High Availability is a system design approach and associated service implementation that ensures a prearranged level of operational performance will be met during a contractual measurement period.

High Availability is about protecting the Service Level Agreements (SLAs) and the agreed Fault Domains

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

Service Level AgreementsAgreed levels of service usually between vendors, suppliers, and clients or inter organisational departments (OLAs)

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

Fault Domains“A Fault Domain is the group of physical or virtual infrastructure pieces with a common configuration that share a single point of failure.”

Fault DomainsWhat am I protecting against?

Building the Franken Rack

Lack of Redundant PowerLack of Redundant Network Connectivity

Building the Franken Rack

Every Rack is BespokeNo Consistency – Hot Spare SourcingThe Datacenter People Hate You

Building the Franken Rack

What about what’s inside?

Fault Domain Fault Domain

Defining Fault Domains

Fault Domain Fault Domain

WE

Disaster Recovery“The process, policies, and procedures that are related to preparing for recovery or continuation of technology infrastructure which are vital to an organization after a natural or human-induced disaster.”

Disaster Recovery is about recovering the critical operations that enable the business to function

Defining RequirementsRecovery 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 RTOExample:RPO of 1 hourRTO of 3 hours

“I can lose 60 minutes worth of data, and all of my data can be inaccessible for three hours.”

RPO/RTO versus CostAs data loss tends to 0, cost tends to $£¥€$£¥€$£¥€

RPO/RTO COST

NH

Datacentre BDatacentre A

SharePoint Farm

Stretched Farms – HA or DR or …..

< 1ms

Stretched FarmsOriginally NOT supported for SP2013“Physical” Data CentreSupported as of April 2013“Logical” Data Centre

For a stretched farm architecture to work as a supported high-availability solution, the following prerequisites must be met:

There is a highly consistent intra-farm latency of <1ms, 99.9% of the time over a period of ten minutes. (Intra-farm latency is commonly defined as the latency between the front-end web servers and the database servers.)

The bandwidth speed must be at least 1 gigabit per second.

http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx#hwLocServers

WE

SQL Server connection stringsIsolate physical dependenciesSQL Aliases and/or DNS A Records

Planning is required!Consider SharePoint database typesConfigure the default database server in Central Admin

AlwaysOn Availability Groups

AlwaysOn Availability GroupsSQL Server 2012“Kind-of” Clustering and MirroringSync CommitTwo sync replicas (three copies)

Async CommitReadable SecondariesBackup Target Selection Failover Cluster

Clustered Resource

Creating an Availability Group

Neil Hodgkinson

AlwaysOn TipsQuorumOdd numberFile Share QuorumVote or no vote

Database Backup LocationCommon file share

Firewall Ports1433, 5022

AlwaysOn TipsChecking for Database Synchronicity – Data loss SELECT sys.databases.database_id, sys.databases.name, sys.dm_hadr_database_replica_states.synchronization_health_desc,sys.dm_hadr_database_replica_states.database_state_desc,sys.dm_hadr_database_replica_states.last_commit_timeFROM sys.dm_hadr_database_replica_states INNER JOIN sys.databasesON sys.databases.database_id = sys.dm_hadr_database_replica_states.database_idWHERE sys.dm_hadr_database_replica_states.database_state is not NULL

RPO/RTO Options

Zero Seconds Minutes Hours Days Weeks

Recovery Point Objective

Reco

very

Tim

e O

bje

ctiv

e

Mirroring - Sync

AlwaysOn - Async

Failover Clustering

Backup/Restore

Mirroring - Async

Log Shipping

AlwaysOn - Sync

NH

High Availability

AlwaysOn Availability GroupsShortest possible RPO and RTOSync-commit between replicas

Database Support – Sync CommitDatabase 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 Yes – NR

Word Automation Yes

WE

AlwaysOn Availability Groups for High AvailabilityNeil Hodgkinson

Demo Environment - Start

SQL 1

FARM3

SQL 2

Demo Environment - End

Failover Cluster

Clustered Resource

SQL 1

FARM3

SQL 2

Demo SummaryDemo 2Create WFSC ClusterBack up DatabasesCreated Always On Group

Added second replicaCreated Listener

Added Databases to the Always on GroupChanged connection string in SharePoint to SQL Listener

PowerShell – SPDatabase.ChangeDatabaseInstance MethodFailover databases to prove HA

NH

Disaster Recovery

SharePoint Disaster RecoveryComplex!Depends on Service Applications and associated DatabasesAsync commit between replicasFailover ProcessesPlannedUnplanned

Strongly Recommended Reading Before Considering Failover Testinghttp://technet.microsoft.com/en-us/library/ff877957.aspx

Search Service ApplicationsRequires different approach to SP2010Options

Search Service Application Backup and RestoreFull Fidelity Captures all Data and Settings

Crawl Production or Crawl Read Only Content DBs in DR FarmLoses Analytics information and search configuration below Service

App Level

Restore SPSearch Administration Database to New Service Application and Recrawl

Captures Configuration Settings but not Analytics information WE

Search Service ApplicationsStrategy

If Search freshness is number one concern on failover to DR Site

Dual crawl production or crawl read only DBs in DR Site

Business critical search configurations at Service App Level

Carry out Search Service Application Backup as standby

WE

If full fidelity search experience is required

Carry out periodic service application backup and restores to DR

Initiate new full crawl on failover to capture deltas

RTO/RPO dictated by restore time and frequency

Other considerationsCustomizationsSolutions deployed to both FarmsSPFarm and SPWebApplication Features activated in secondaryMay need to re-scope Features

Configuration changesReplay in secondary if persisted to ConfigDB

Database Support – Async CommitDatabase Supported

Admin Content No

App Management TBD

BDC TBD

Config No

Content Yes

Managed Metadata TBD

PerformancePoint TBD

PowerPivot Not Tested

Project TBD

Search Analytic Reporting No

Search Admin No

Database Supported

Search Crawl No

Search Links No

Secure Store TBD

State Service No

Subscription Settings TBD

Translation Services TBD

UPA Profile TBD

UPA Social TBD

UPA Sync TBD

Usage TBD

Word Automation TBDAnnouncement!!

!!

Database Support – Async CommitDatabase 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

PowerShell IntegrationAdd-DatabaseToAvailabilityGroupAdds databases to availability group

Remove-DatabaseFromAvailabilityGroupRemoves databases from availability group

Get-AvailabilityGroupStatusChecks the status of an existing availability group

AlwaysOn Availability Groups for Warm Standby Neil Hodgkinson

Demo Environment - Start

SQL 1

FARM 3

SQL 2

FARM 4

SQL 3

Clustered Resources

ProductionSeattle

DRNew York

Failover Cluster

Demo Environment - End

SQL 1

FARM 1

SQL 2

FARM 2

SQL 3

ProductionSeattle

DRNew York

Failover Cluster

Clustered Resource

Demo SummaryDemo 3Built DR Farm with temp Content DB databaseAdd server to clusterReconfigure AlwaysOn Availability Group Attach replicated Content DBFailover all Content and Services Databases to async nodeAttached Content Databases to WebApplicationsCreated Service Applications

NH

Wrap Up

In Review: Session Objectives And TakeawaysUnderstand the concepts of Business Continuity and the implications for SharePointDifferentiate between High Availability and Disaster Recovery Gain a deeper understanding of using SQL Server AlwaysOn for implementing HA/DR for SharePoint Announcement of changes!

Questions

MySPCSponsored by

connect. reimagine. transform.

Evaluate sessionson MySPC using yourlaptop or mobile device:myspc.sharepointconference.com

© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.