SQL Server 2014

Platform for Hybrid Cloud

(Level 300 Deck)
SQL Server 2014
Platform for Hybrid Cloud
(Level 300 Deck)
SQL Server 2014
Platform for Hybrid Cloud
(Level 300 Deck)
SQL Server 2014
Platform for hybrid cloud
Level 300
Hybrid cloud solutions

Restore to VM
Geo-replication
Backup to Cloud
Backup to Cloud
Backup to Windows Azure

CREATE CREDENTIAL mystoragecred

WITH IDENTITY = ‘mystorage',
SECRET = ‘<your storage access key>

BACKUP DATABASE mydb TO URL ='https://mystorage.blob.core.windows.net/backup-

container/mydb-20130411.bak'
WITH CREDENTIAL = ‘mystoragecred',
FORMAT, COMPRESSION, STATS = 5,
MEDIANAME = ‘mydb backup 20130411', MEDIADESCRIPTION = 'Backup of mydb'
Backup to Windows Azure

Windows Azure storage

• On-site/off-site storage costs • Near “bottomless” storage

• Device management costs • Off-site, geo-redundant
• No provisioning
• XDrives limited to 1 terabyte • No device management
• Max 16 drives • Media safety (decay-free)
• Manage drives and policy • Remote accessibility
Backup to Windows Azure
Backup to Windows Azure Tool
Managed Backup to Azure

• Agent that manages and automates SQL Server backup policy

• Large-scale management and no need to manage backup policy

• Context-aware – for example, workload/throttling
• Minimal knobs – control retention period
Example:
• Manage whole instance or particular databases
EXEC smart_admin.sp_set_db_backup
• Take advantage of backup to Azure @database_name='TestDB',
• Inherently off-site @storage_url=<storage url>,
@retention_days=30,
• Geo-redundant
@credential_name='MyCredential',
• Minimal storage costs @enable_backup=1
• Zero hardware management
Cloud DR
Cloud DR
Hybrid cloud solutions
Why Do We Need Cloud DR for SQL Server?

• An event can cause on-premises

SQL Server to become unavailable
‐ Temporarily (e.g. gateway failure)
‐ Permanently (e.g. flooding)
• A disaster recovery site is expensive
‐ Site rent + maintenance
‐ Hardware
‐ Ops

18
Typical Configuration

19
Characteristic of Cloud DR for SQL Server

• Deploy one or more secondary replicas for on-premises

SQL Server
‐ Replicas continuously synchronize
• At best region: West US, East US, East Asia, Southeast
Asia, North Europe, West Europe
‐ Political considerations
‐ Latency
• Low TCO
‐ VM and storage
20
Inverse Deployment Configuration Supported

21
Technologies Supported

Technology SQL Server Version Zero Data Loss Scope # Secondaries Automatic Readable
Failover Secondaries
Availability SQL Server 2012 Yes* DB(s) 4 Yes Yes
Groups (Sync Mode) (w/
additional
cluster
member)**
Database SQL Server 2008 R2 Yes* DB 1 Yes Limited
Mirroring SQL Server 2012 (High Safety (w/ (database
Mode) Witness)** snapshots)
Log SQL Server 2008 R2 No DB N No Limited
Shipping SQL Server 2012 (standby
state)

* Most customers use Async Mode (High Performance) to avoid impacting primary performance
**Async Mode only supports Force Failover to make DR (and potential data loss) a conscious decision
22
Availability Groups in Cloud DR

• Provide additional benefits:

‐ Integrated HA/DR
‐ Offload Read workloads to Windows Azure
 Connect reporting/BI apps
 Migrate apps and run against local secondaries

‐ Offload Backups to Windows Azure

 A solution for policy compliance

• Requires:
‐ Same Windows Domain
‐ Needs an Active Directory Domain Controller
23
Example of Availability
Group Spanning On-premises and Windows Azure

redmond.corp.microsoft.com
Availability uswest.internal.cloudapp.net

CSNB2252108- Virtual
Network

CSNB2252109-TA VPN Device

Windows
Cluster AGHybrid2

24
Customer deployment examples

Online travel firm

Container shipping company
Online video streaming company
Healthcare company

25
Online Travel Firm

• Business
‐ Leading tour operator in Europe.
‐ Sells trips to holiday destinations throughout Europe.
‐ 10 brands, 9 countries
‐ Over 700K passengers in 2011
• Application
‐ Online travel reservation system
• Infrastructure
‐ 1 data center (on-premises)
‐ Use AlwaysOn Availability Groups on-premises today
‐ No DR site
‐ Leverage Windows Azure as DR data center

26
Architecture Diagram
On-Premises
Windows Cluster

Availability Group

Primary Secondary

27
Architecture Diagram
On-Premises Cloud
Windows Cluster

Availability Group

PrimarySecondary
Secondary

28
Container Shipping Company

• Business
‐ One of the largest container shipping company in the World
• Application
‐ Secured electronic data interchange (EDI) messages
• Infrastructure
‐ Primary data center in NJ
‐ DR data center in Manhattan, NY
‐ Use Availability Groups for DR
‐ Both data centers got affected by Hurricane Sandy
‐ Would like to leverage Windows Azure as DR data center

29
Architecture Diagram
On-Premises (NY) On-Premises (NJ)
Windows Cluster Windows Cluster

Availability Group Availability Group

Primary Secondary

30
Architecture Diagram
On-Premises (NY) On-Premises (NJ)
Windows Cluster Windows

Availability Group Availability

Primary Secondar
y

Cloud

Secondary

31
Online Video Streaming Company

• Characteristics:
‐ Organizational strategy to move to Windows Azure
‐ HA / DR important need
‐ Windows Azure will be used as primary
‐ One secondary in Windows Azure for local HA
‐ Another secondary replica on-premises for DR

32
Architecture Diagram
Cloud On-Premises
Windows Cluster

Availability Group

Secondary
Primary Secondary

33
Healthcare Company

• Characteristics:
‐ Healthcare software company providing on premises as well as
hosted software
‐ Use Windows Azure as hosting infrastructure
‐ HA / DR needs are important
‐ HIPAA compliance is important
‐ Primary: Windows Azure
‐ Secondary: a copy of data on premises for reporting and
regulatory purposes

34
Architecture Diagram
Cloud On-Premises
Windows Cluster

Availability Group

Secondary
Primary Secondary

35
AlwaysOn Replica in Windows Azure

• What’s being delivered

‐ Wizard to add a replica in a Windows Azure VM
• Main benefits
‐ Easily deploy one or more replicas of your
databases to Windows Azure
 No need for a DR site (hardware, rent, ops)

‐ Use these replicas for

 Disaster Recovery
 Workloads (reads/backups)

36
Deploy dB to
Windows Azure Wizard
Deploy dB to
Windows Azure Wizard
Easy on-ramp to cloud
Deploy databases to Windows Azure VM

• New wizard to deploy databases to SQL Server

in Windows Azure VM
• Can also create a new Windows Azure VM
if needed

• Easy to use
• Perfect for database administrators new to Azure
and for ad hoc scenarios
• Complexity hidden
• Detailed Azure knowledge not needed
• Almost no overhead: defining factor for time-to-
transfer is database size
SQL Server Data & Log
Files in Windows Azure
Storage
SQL Server Data & Log
Files in Windows Azure
Storage
SQL Server Data & Log Files in Windows Azure Storage

• Ability to move data & log files in

Windows Azure Storage, while keeping
the compute node of SQL Server on-
premise
• Transparent Data Encryption (TDE) is supported

• No application changes required

• Centralized copy of data and log files
• Enjoy unlimited storage capacity in Azure
Storage (built in HA, SLA, geo-DR)
• Secure because TDE encryption key can be
stored on-premise
• Restore database is simply an attach operation
SQL Server Data & Log Files in Windows Azure Storage
Complete and consistent data platform
Call to action Download SQL Server 2014 CTP2

Stay tuned for availability

www.microsoft.com/sqlserver
© 2013 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