23 mai 2015
SharePoint
Saturday
Montréal
SQL Server AlwaysOn Deep Dive
for SharePoint Administrators
SQL Server
AlwaysOn Deep Dive
for
SharePoint
Edwin Sarmiento
http://www.EdwinMSarmiento.com
[email protected]
@EdwinMSarmiento
http://ca.linkedin.com/in/EdwinMSarmiento
just when you
think it’s an
high
characteristic of a system that is
f u l l y o p e r a t i o n a l
for a long period of time
high
availability
is
N O T
the same as
UPTIME
high
Just because
something is
UP
doesn’t mean it’s
available
UP
downtime
ZERO
data loss
&
Recovery Time Objective
( R T O )
When is my application coming back?
high
(one “nine”)
%
availability
90
36.5 days
per year
72 hours
per month
16.8 hours
per week
do
wntime
(two “nines”)
%
availability
99
3.65 days
per year
7.2 hours
per month
1.68 hours
per week
do
wntime
(three “nines”)
%
availability
99
.
9
8.76 hours
per year
43.8 minutes
per month
10.1 minutes
per week
do
wntime
(four “nines”)
%
availability
99
.
99
52.56 minutes
per year
4.32 minutes
per month
1.01 minutes
per week
do
wntime
(five “nines”)
%
availability
99
.
999
5.26 minutes
per year
25.9 seconds
per month
6.05 seconds
per week
do
wntime
RTO
Maximum outage:
+4 hours
September 11,
2001 10:00AM
4 hours
(five “nines”)
%
availability
99
.
999
5.26 minutes
per year
25.9 seconds
per month
6.05 seconds
per week
do
wntime
How long does it take to
restart
high
availability
disaster
recovery
disaster
recovery
characteristic of a system that is
o p e r a t i o n a l l y a c c e p t a b l e
after a disaster
Recovery Point Objective
( R P O )
How much data can I afford to lose?
disaster
recovery
RPO
Maximum outage:
-4 hours
September 11,
2001 10:00AM
4 hours
0
10000
20000
30000
40000
50000
60000
70000
1
2
3
4
5
6
7
8
9
10
11
C
ost
Time
downtime
ZERO
data loss
&
architecture
diagrams
recommended only for
DEVELOPMENT ENVIRONMENT
which usually ends up being so popular
that it has now become a
MISSION-CRITICAL PRODUCTION SERVER
http://portal.testdomain.com*
Web, Application and Database Server
Single-Server Deployment
http://portal.testdomain.com*
Web and Application Server
Database Server
Basic 2-Tier Architecture
http://portal.testdomain.com*
Web Server
Database Server
Application Server
Scalability& High Availability
*alternate access mappings (AAM) configured
http://portal.testdomain.com*
Web Server
Database Server
Application Server
Scalability &High Availability
hardware load balancer
*alternate access mappings (AAM) configured
http://portal.testdomain.com*
Web Server
Database Server
Application Server
Scalability &High Availability
hardware load balancer
*alternate access mappings (AAM) configured
3-Tier Architecture
Local High Availability Disaster Recovery
Web & Application Server
Failover Clustered Instances
Availability Groups
*
INSTANCE
protection
can either be an HA and/or DR solution
log
data
failover clustering
how it works
Windows Server Failover Cluster
SQL Server2-node
cluster
log
data
Windows Server Failover Cluster
SQL ServerApplication
2-node
cluster
traditional
log
data
Windows Server Failover Cluster
SQL ServerApplication
failover clustering
how it works
2-node
cluster
*
DATABASE (group)
protection
can either be an
HA and/or DR solution
*
DATABASE (group)
protection
combination of
DATABASE MIRRORING
&
FAILOVER CLUSTERING
SQL Server
log
data
SQL Server
log
data
Secondary Replica
Primary Replica
SQL Server
log
data
Secondary Replica
*maximum of
EIGHT
replicas
Windows Server Failover Cluster
http://portal.testdomain.com*
Web Server
Database Server
Application Server
Scalability & High Availability
hardware load balancer
*alternate access mappings (AAM) configured
3-Tier Architecture
Local High Availability Disaster Recovery
Web & Application Server
Failover Clustered Instances
Availability Groups
SQL Server
Availability Groups
COMMON DESIGN PATTERNS
What will be your
QUORUM
model?
SQL Server
Availability Groups
COMMON DESIGN PATTERNS
What will be your
REPLICATION MODE
?
SQL Server
Availability Groups
COMMON DESIGN PATTERNS
What will be your
NETWORK
CONFIGURATION
?
SQL Server
Availability Groups
COMMON DESIGN PATTERNS
What will be your
LICENSING MODE
?
SQL Server
Availability Groups
COMMON DESIGN PATTERNS
SQL Server
log
data
SQL Server
log
data
Secondary Replica
Primary Replica
PRODUCTION
2 Replicas
, Stand-alone instances (HA only)
SQL Server
log
data
SQL Server
log
data
Secondary Replica
Primary Replica
PRODUCTION
SQL Server
log
data
Secondary Replica
DR
*
You need to discuss this with your network team
Windows Server Failover Cluster
*
NO VOTE
2008/2012
*LowerQuorumPriorityNodeID
2012 R2
SQL Server
log
data
Primary Replica
PRODUCTION
SQL Server
log
data
Secondary Replica
DR
*
You lose the ability to do automatic failover
Windows Server Failover Cluster
*
NO VOTE
2008/2012
*LowerQuorumPriorityNodeID
2012 R2
SQL Server
log
data
Primary Replica
PRODUCTION
SQL Server
log
data
Secondary Replica
Additional Data Center
SQL Server
log
data
Secondary Replica
DR
*
You lose the ability to do automatic failover
Windows Server Failover Cluster
*
NO VOTE
2008/2012 *LowerQuorumPriorityNodeID 2012 R2 *NO VOTE
2008/2012 *LowerQuorumPriorityNodeID 2012 R2SQL Server
log
data
Primary Replica
PRODUCTION
DR
SQL Server
log
data
Secondary Replica
*
You lose the ability to do automatic failover
Windows Server Failover Cluster
2 Replicas
, FCI (HA + DR)
*
NO VOTE
2008/2012
*LowerQuorumPriorityNodeID
