Transcript SharePoint Business Continuity Management with SQL Server

Pre-Microsoft
Process 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
Contact
Email – [email protected]
Twitter - @nellymo
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
Definitions
SQL Server AlwaysOn Overview
SharePoint High Availability
SharePoint Disaster Recovery
Recent Support Changes
Agreed 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
WE
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
Example:
RPO of 1 hour
RTO of 3 hours
“I can lose 60 minutes worth
of data, and all of my data
can be inaccessible for three
hours.”
RPO
RTO
As data loss tends to 0, cost tends to $£¥€$£¥€$£¥€
RPO/RTO
COST
NH
SharePoint Farm
< 1ms
Datacentre A
Datacentre B
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
Isolate physical dependencies
SQL Aliases and/or DNS A Records
Planning is required!
Consider SharePoint database types
Configure the default database server in Central Admin
SQL Server 2012
“Kind-of” Clustering and Mirroring
Sync Commit
Async Commit
Readable Secondaries
Backup Target Selection
Clustered Resource
Failover Cluster
Quorum
Odd number
File Share Quorum
Vote or no vote
Database Backup Location
Common file share
Firewall Ports
1433, 5022
Checking 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_time
FROM sys.dm_hadr_database_replica_states
INNER JOIN sys.databases
ON sys.databases.database_id = sys.dm_hadr_database_replica_states.database_id
WHERE sys.dm_hadr_database_replica_states.database_state is not NULL
Backup/Restore
Log Shipping
Mirroring - Async
AlwaysOn - Async
Failover Clustering
Mirroring - Sync
AlwaysOn - Sync
Zero
Seconds
Minutes
Hours
Days
Weeks
NH
Database
Supported
Database
Supported
Admin Content
Yes
Search Crawl
Yes
App Management
Yes
Search Links
Yes
BDC
Yes
Secure Store
Yes
Config
Yes
State Service
Yes
Content
Yes
Subscription Settings
Yes
Managed Metadata
Yes
Translation Services
Yes
PerformancePoint
Yes
UPA Profile
Yes
PowerPivot
Not Tested
UPA Social
Yes
Project
Yes
UPA Sync
Yes
Search Analytic Reporting
Yes
Usage
Yes – NR
Search Admin
Yes
Word Automation
Yes
WE
FARM3
SQL 1
SQL 2
FARM3
Clustered Resource
SQL 1
SQL 2
Failover Cluster
Create WFSC Cluster
Back up Databases
Created Always On Group
Added second replica
Created Listener
Added Databases to the Always on Group
Changed connection string in SharePoint to SQL Listener
PowerShell – SPDatabase.ChangeDatabaseInstance Method
Failover databases to prove HA
NH
Strongly Recommended Reading Before Considering Failover Testing
http://technet.microsoft.com/en-us/library/ff877957.aspx
Options
WE
WE
Solutions deployed to both Farms
SPFarm and SPWebApplication Features activated in secondary
May need to re-scope Features
Replay in secondary if persisted to ConfigDB
Database
Supported
Database
Supported
Admin Content
No
Search Crawl
No
App Management
TBD
Search Links
No
BDC
TBD
Secure Store
TBD
Config
No
State Service
No
Content
Yes
Subscription Settings
TBD
Managed Metadata
TBD
Translation Services
TBD
PerformancePoint
TBD
UPA Profile
TBD
PowerPivot
Not Tested
UPA Social
TBD
Project
TBD
UPA Sync
TBD
Search Analytic Reporting
No
Usage
TBD
Search Admin
No
Word Automation
TBD
Database
Supported
Database
Supported
Admin Content
No
Search Crawl
No
App Management
Yes
Search Links
No
BDC
Yes
Secure Store
Yes
Config
No
State Service
No
Content
Yes
Subscription Settings
Yes
Managed Metadata
Yes
Translation Services
Yes
PerformancePoint
Yes
UPA Profile
Yes
PowerPivot
Not Tested*
UPA Social
Yes
Project
Yes
UPA Sync
No
Search Analytic Reporting
No
Usage
Yes – NR
Search Admin
No
Word Automation
Yes
WE
Adds databases to availability group
Removes databases from availability group
Checks the status of an existing availability group
FARM 3
FARM 4
Clustered Resources
SQL 1
SQL 2
Failover Cluster
SQL 3
FARM 1
FARM 2
Clustered Resource
SQL 1
SQL 2
Failover Cluster
SQL 3
Built DR Farm with temp Content DB database
Add server to cluster
Reconfigure AlwaysOn Availability Group
Attach replicated Content DB
Failover all Content and Services Databases to async node
Attached Content Databases to WebApplications
Created Service Applications
NH
Sponsored by