SPC335: Deploying SharePoint 2010 as a Mission Critical Application

makeshiftklipInternet and Web Development

Oct 31, 2013 (3 years and 9 months ago)

99 views


http://sharepoint.microsoft.com/blogs/fromthefield
samhassa@microsoft.com

@
samhassa

chwhite@microsoft.com

@
mrwhitey

99.999%
99.99%
99.9%
99%
~ 5 minutes

< 1 hour

9 hours

87 hours

Class

RTO

RPO

Tier 1

>99.99%

1 Hour / Year

< 5

Min

Tier 2

99.9%
-

99.99%

1

Hour/Year


8.5 Hours/Year

5 Min


8.5 Hours

Tier 3

<99.9%

Hours

/Days

Hours
/
Days

10%

20%

30%

20%

20%

Botched Maintenance
Web Server Capacity
SQL Server Capacity
Hardware Failure
Miscellaneous
Redundant:

Switches

SharePoint
Servers

Database
Servers

Storage

Power Supplies

SQL Server
Cluster

SharePoint Servers

Shared Disk
Array

Node A

Node

B

Heartbeat

Mode

Safety Level

Transfer Mechanism

Failover

High Safety/Protection

Full (no witness)

Synchronous

Manual

High Availability

Full (with witness)

Synchronous

Manual and Automatic

High Performance

Off

Asynchronous

Forced


Witness Ser ver

Principal

Mirror

Encrypted
Channel

I’m OK!

New

Principal

Principal

Down!

3

4

2

1

2

5

$db
=
Get
-
SPDatabase

|
Where

{
$_
.Name
-
match
"DatabaseName"
}


$
db
.
AddFailoverServerInstance(
"MirrorServerName"
)

$db
.
Update
()

Secondary Data Center

Primary Data Center

Load

Balancer

WFE

WFE

SQL Principal

SQL Mirror

SQL Witness

SQL Principal

SQL Mirror

Criteria

Failover Clustering

High
-
Availability Mirroring

Data Loss

None

None

Time to Failover

30 sec



2 min

10 sec


1 min

Failover Type

Automatic

Automatic

Location Requirements

Nodes

on same subnet

Same LAN (1ms latency max.)

Protects

Instance but not failed storage

Database and failed storage

Hardware Requirement

Yes


shared storage

No

Recovery Model Requirement

None

Full

Cross Edition Compatibility

N/A

No*

(witness only)

FILESTREAM Support

Yes

No

Performance Overhead

Some may occur during failover

Memory, processor and network,

transactional latency can also occur

Operational Burden

Server level

Yes, all databases,

manual
reconfiguration after failover

transactional latency can also occur

Service Application

Database

Supported?

N/A

Content

Y

Search

Administration

Crawl

Property

N

N

N

User Profile

Profile

Synchronization

Social Tagging

N

N

Y*

Managed Metadata

Managed Metadata

Y*

Web Analytics

Staging

Repor ting

Y**

Y**

Usage and Health Data Collection

Logging

Y***

Secure Store

Secure Store

Y

Service Application

Database

Supported?

PerformancePoint

PerformancePoint

Y

Business

Data Connectivity

Business

Data Connectivity

N

Subscription Settings

Subscription Settings

N

Word Automation

Word Automation

N

Application

Registry

Application

Registry

N

State

State

N

http
://
technet.microsoft.com/en
-
us/library/cc663011.aspx
$db
=
Get
-
SPContentDatabase

-
Identity
"DatabaseName
"


$
db
.
RefreshSitesInConfigurationDatabase()

Criteria

Log Shipping

Asynchronous

Mirroring

Data Loss

Yes

since last copy job

Potentially

some

Time to Failover

Minutes

Minutes

Failover Type

Manual

Manual

Location Requirements

None

None

Protects

Database and failed storage

Database and failed storage

Hardware Requirement

No

No

Recovery Model Requirement

Bulk/Full

Full

Cross Edition Compatibility

Yes

No

FILESTREAM Support

Yes

No

Performance Overhead

Network

during copy job

Memory, processor and network

Operational Burden

Yes, all databases,

manual
reconfiguration after failover

Yes,

a
ll databases,

manual
reconfiguration after failover

Read
-
Only Mode

Yes


but disconnect

users first

No


use SQL

Server Snapshots

http://
technet.microsoft.com/en
-
us/library/cc748824.aspx
http://
technet.microsoft.com/en
-
us/library/ff628971.aspx
http://technet.microsoft.com/en
-
us/library/cc663011.aspx