425.922.9081425.922.9081

Business Continuity Solutions for SQL Database* applications on Windows AzureAlexander (Sasha) NosovPrincipal Program ManagerMicrosoft Corporation

* Formerly known as SQL Azure 425.922.9081

DBI334

425.922.9081

Business Continuity problems

425.922.9081

Platform security

Foundation of Business Continuity

Physical security Geo distribution

Compliance

425.922.9081

Terminology

425.922.9081

Availability challenges in cloud systems

Hardware and software failures are inevitablePeople make operational errors that cause failuresAt cloud scale low frequency failures happen every day

Need: automated fault tolerance to maintain local availability

425.922.9081

High Availability solution for SQL databases

Reads are completed at the primaryWrites are replicated to secondariesEach replica is backed up independently

DB

Single LogicalDatabase Multiple Physical

Replicas

P

SS WriteWrite

AckAck

ReadValue WriteAck

P

S

S

425.922.9081

High Availability under the hood

Critical capabilities:Create new replicaSynchronize data Stay consistentDetect failuresFail over

Primary Manager Node

Partition Manager

Fabric

Data Node 103

P

SS

Data Node 104

SS

Data Node 102

P

SS

Data Node 105

PSS

Data Node 101

SP

P

P

S SS

Global Partition

Map

Node down

Which replica lost?

Pro

mote

to

pri

mary

Reconfigure

S

425.922.9081

Customer benefits of High Availability

No additional administration costACID properties are maintained by the systemFailovers are fully automatedDynamic routing of connectionsNo additional charges for database redundancyRPO=0, RTO=30sec99.9% availability SLA

425.922.9081

425.922.9081

Recovery from human errors

Humans make mistakesThe system cannot detect themHuman is needed to recover

Need: ability to return to previous application state

425.922.9081

Database copy as extension of Create replica

425.922.9081

Database copy as extension of Create replica

Extends replica creation and expose to userTransactional consistency after completionCan copy to any server in the same regionCan copy from live databaseCan cancel in flight operationCan monitor statusOnly billed if copy is successful

S

S

P

P’

S

S

425.922.9081

Using database copy to recover from human error

425.922.9081

AzureDNS

Hostname IP Address

www.contoso.com North Central UShttp://www.contoso.com/

Contoso service

South Central US

App admin

End user

DB

Co

py

Create backup copy

DB_06_11_2012

DB_06_12_2012

DB_06_13_2012

Oops!

Recover from backup

DB_MAINDB_MAIN_OLD

ALTER DATABASE DB_MAINMODIFY NAME = DB_MAIN_OLD GO WAITFOR DELAY '00:00:30' GO ALTER DATABASE DB_06_01_2012 MODIFY NAME = DB_MAIN GODB_MAIN

Using database copy to recover from human error

Minimal charge is prorated day useCopies entire databaseYou are responsible for retention and cleanupSupport database federations is coming soonRTO = time to recognize the error + time to rename the database + rename delays

425.922.9081

Using database copy and Azure storage

Leverages import/export service and Azure storageReduces storage cost but increases backup timeMore complex backup/restore workflowRTO = time to recognize the error + time to import database + time to rename the database

Contoso service

South Central US

DB

Co

py

DB_06_01_2012

DB_MAIN

BP_06_11_2012

BP_06_12_2012

BP_06_13_2012

Expor

t

425.922.9081

425.922.9081

Recovery from widespread loss of facility

Happen more often than you thinkOften caused by human errorRecovery will cause data and uptime loss

Need: geographic redundancy and ability to fail over

425.922.9081

Using export to Azure storage to recover from widespread failure

425.922.9081

AzureDNS

Hostname IP Address

www.contoso.com South Central UShttp://www.contoso.com/

Contoso V1

(primary instance)

South Central US

App admin

End user

DB

Co

py

Create backup copy

DB_06_11_2012

DB_06_12_2012DB_06_13_2012

DB_MAINContoso V1 (secondary instance)

North Central US

DB_MAIN

BP_06_11_2012

BP_06_12_2012

BP_06_13_2012

Export to blob

Export

Import

from blob

Impor

t

Activate and verify application

DNS update

North Central US

Using Azure storage for geo redundancy

Copies entire databaseYou are responsible for cleanupMinimal database charge is prorated day useSupport for database federations is coming soonRTO = time to import + time to start app + DNS changeRPO = export interval

demo

Using SQL Database import/export service for disaster recovery of your application

425.922.9081

Contoso V1

(primary

instance)

South Central US

DB

Co

py

DB_06_01_2012

DB_05_25_2012

DB_05_18_2012

North Central US

BP_06_11_2012

BP_06_12_2012

BP_06_13_2012

Geo-replicationBP_06_11_2012

BP_06_12_2012

BP_06_13_2012

Using Azure storage automatic geo-replication

425.922.9081

Using Azure storage automatic geo-replication

Quicker export to local blobRPO = export interval (potentially shorter)RTO = Azure storage RT (24 hrs) + time to import + time to start app + DNS change

425.922.9081

425.922.9081

Quick survey

❶ I am fully satisfied with the existing Azure solutions

❷ I am OK for now but the achievable RPO/RTO will be a problem down the road

❸ The achievable RPO/RTO do not meet my SLA requirements

425.922.9081

Roadmap: Geo-DR

425.922.9081

Roadmap: Geo-DR

Extends replica creation and data synchronization to geoUser initiatedAutomatic data replication and synchronizationOptional RPO enforcementRead-only geo-secondaryMultiple geo-secondariesUser-controlled failover

P’

S’

S’ P

S

S

425.922.9081

Roadmap: Point in time recovery

425.922.9081

Roadmap: Point in time recovery

S

S

P

P’

Exposes internal backups to the userBackups are highly availableRestores to new databaseAny point in time within retention period

425.922.9081

Recap and call to actionAzure provides a solid foundation of business continuityA range of solutions availableUser participation is required:

Implement re-try logic in the application Enable PITR using dbcopy

Convert to BACPAC and blobs to minimize cost

Enable geo-redundancy by exporting BACPAC(s) into multiple datacenters

Stay tuned for future announcement of the new BC features

425.922.9081

Track Resources

@sqlserver@ms_teched

mvaMicrosoft Virtual Academy

SQL Server 2012 Eval Copy

Get Certified!

Hands-On Labs

425.922.9081

Additional resources

Business Continuity in SQL Azurehttp://msdn.microsoft.com/en-us/library/windowsazure/hh852669.aspx

Business Continuity for Windows Azurehttp://msdn.microsoft.com/en-us/library/windowsazure/hh873027.aspx

Inside SQL Azurehttp://social.technet.microsoft.com/wiki/contents/articles/1695.inside-sql-azure.aspx

SQL Azure Import/Export Service has hit Productionhttp://dacguy.wordpress.com/

425.922.9081

Related Content

Breakout Session: AZR203 Business Continuity in the Windows Azure CloudAZR204 Hybrid Will Rule: Options to Connect, Extend and Integrate Applications in Your Data Center and Windows Azure

Find Me Later At SQL Server booth or e-mail sashan@microsoft.com

425.922.9081

Q & A

425.922.9081

Using Data Sync as a DR solution

Goals of Data Sync

Synchronization of data between SQL Server databases and Azure SQL databases.

Synchronization of data between two or more Azure SQL databases

Challenges

Preservation of transaction boundaries

Some schemas are not supportedNo support for multiple versions

425.922.9081

Track Resources

@sqlserver@ms_teched

mvaMicrosoft Virtual Academy

SQL Server 2012 Eval Copy

Get Certified!

Hands-On Labs

425.922.9081

Resources

Connect. Share. Discuss.

http://northamerica.msteched.com

Learning

Microsoft Certification & Training Resources

www.microsoft.com/learning

TechNet

Resources for IT Professionals

http://microsoft.com/technet

Resources for Developers

http://microsoft.com/msdn

Complete an evaluation on CommNet and enter to win!

425.922.9081

MS Tag

Scan the Tagto evaluate thissession now onmyTechEd Mobile

425.922.9081

Session Objectives and Takeaways

Session Objectives: Scope of business continuity failuresBusiness continuity solutions for SQL database application in Windows AzureImplementation trade-offs

Key Takeaways:Azure provides strong support to enable business continuity of your applicationYou can choose from a range of solutions depending on your SLA requirements and budget constraints

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.