1EMC CONFIDENTIAL—INTERNAL USE ONLY Overview of SQL Server 2012 High Availability and Disaster...

1EMC CONFIDENTIAL—INTERNAL USE ONLY

Overview of SQL Server 2012

High Availability and Disaster Recovery (HADR)

Wei FanTechnical Partner Management – MicrosoftJanuary 2012


Agenda• Business Case for HADR

• Prior to SQL Server 2012: HADR Review

• What is New in HADR of SQL Server 2012

• Demo

• Q & A

Footer information: 10 pt. MetaNormalLF—NOT italics


Business Case for HADR

• Data loss

• Downtime


Business Risks and Solutions

Business Risk Solution

High Availability

Potential downtime ofdatabase service

Redundant database system components

Disaster Recovery

In case that database service is down with potential data loss, get database service back online with minimum impact

Redundant data. Redundant database system components .


HADR Strategy Principle: Redundancy

Data Redundancy

Database Service Redundancy

Hardware Redundancy


History of SQL-based Data Redundancy• SQL Backup and Restore (SQL Server 6.5)

• SQL Log Shipping (SQL Server 7.0)

• SQL Transactional Replication (SQL Server 7.0)

• SQL Failover Cluster (SQL Server 7.0)

- HADR Enhancements (SQL Server 2000)

• SQL Snapshot (SQL Server 2005)

• SQL Mirroring (SQL Server 2005)

- HADR Enhancements (SQL Server 2008 & R2)

• SQL AlwaysOn (SQL Server 2012)


Permitted downtime (planned & unplanned)

Uptime SLA Downtimeper Year

Downtimeper Month

95% 18.25 days 36 hours

98% 7.30 days 14.4 hours

99% 3.65 days 7.20 hours

99.9% 8.76 hours 43.8 minutes

99.99% 52.6 minutes 4.38 minutes

99.999% 5.26 minutes 0.438 minutes

99.9999% 31.5 seconds 2.59 seconds


SQL HADR Categories by Standby Modes

Standby

ModeFailover Behavior SQL Server Feature

Coldstand

by

• Manual intervention required to ready data copy

• Backup and restore

Warm stand

by

• Data copy ready to use

• Manual failover required

• Transaction log shipping

• Transactional replication

• Database mirroring

Hot stand

by

• Automatic failover • Database mirroring• Failover clustering• AlwaysOn


SQL HADR Categories by DB/Instance HADR

Prior to SQL 2012

SQL 2012

Database Level HADR

Backup and RestoreLog ShippingTransactional Replication

SQL SnapshotSQL Mirroring

AlwaysOn High Availability Group

Instance Level HADR SQL Failover Cluster AlwaysOn Failover Cluster


SQL HADR Review

Prior to SQL Server 2012


Database Backup & Restore

Full Database BackupDifferential Database BackupTransaction Log Backup


Pros & Cons: Database Backup & Restore

Pros: Physical database backup

filesSimple and easy to perform

Cons:Not a high availability

solutionPossible data loss


Scorecard: AlwaysOn vs. Backup & Restore


Log Shipping

Continuous backup and restore

Standby server

Asynchronous


Pros & Cons: Log Shipping

Pros: Automatic restore processMultiple secondary servers

Cons:Possible data lossManual failoverIssue with reporting in standby

server


Scorecard : AlwaysOn vs. Log Shipping


Transactional Replication

Transactional Replication


Pros & Cons: Transactional Replication

Pros: Automatic restore processSecondary servers for

reporting appMultiple secondary servers

Cons:Designed for data, not for

schemaManual failover


Scorecard : AlwaysOn vs. SQL Replication


SQL Failover Cluster Instance: FCI

• Instance level


Pros & Cons: SQL Failover Cluster Instance

Pros: High availability solutionAutomatic failover No lost data Coupled with SAN as shared

arrayCons:

High cost Restricted to local subnet


Scorecard : AlwaysOn FC vs. SQL FC


Database Snapshot

Data-pageCopy-on-write


Pros & Cons: Database Snapshot

Pros: Maintaining historical data Snapshot as a reporting

databaseMany snapshots

Cons:Depend on the primary

databaseRestriction of same server

instance


Scorecard: AlwaysOn vs. SQL Snapshot


Database Mirroring

Hot standby databaseSync/Async modes


Pros & Cons: Database Mirroring

Pros: Sync mode with automatic

failover Async mode for performanceEasy to setup

Cons:Single databaseStandby server not accessible


Scorecard : AlwaysOn vs. SQL Mirroring


SQL Server 2012 HADR

AlwaysOn High Availability Group (HAG)

AlwaysOn Failover Cluster Instance (FCI)


AlwaysOn: High Availability Group

• Installation

• Windows cluster

• No-clustered SQL Server


Configure High Availability Group (AlwaysOn)

• Replica• Database level• Many databases• Failover in groups • Multiple replicas• Sync/Async mode


High Availability Group: Active Secondary

R/W work loadPrimary backupSecondary backup


High Availability Group: Active Secondary


Pros & Cons: High Availability Group

Pros: Synchronous/asynchronous modeFailover on multiple databasesAutomatic failoverUp to 4 replicasActive replicas

Cons:Perf issue in provisioning large databasesPerf issue when updating indexes on large

databases


AlwaysOn: Failover Cluster Instance - FCI

• Instance level• Multi-subnet


Scorecard: AlwaysOn HAG vs. AlwaysOn FC


AlwaysOn Failover: FCI + HA


EMC MV/CE

• Combines Microsoft Failover Cluster and EMC Mirror View• Support failover in storage level• Geographical cluster• Synchronous/Asnychronous mode


Scorecard : AlwaysOn vs. EMC MV/CE


Demonstration


Q&A

1EMC CONFIDENTIAL—INTERNAL USE ONLY Overview of SQL Server 2012 High Availability and Disaster...

Documents

Transcript of 1EMC CONFIDENTIAL—INTERNAL USE ONLY Overview of SQL Server 2012 High Availability and Disaster...