Floating on a Hybrid Cloud: SQL Server 2012 & Microsoft Azure. Timothy P. McAliley Microsoft Premier Field Engineer SQL Server

Transcription

1 Floating on a Hybrid Cloud: SQL Server 2012 & Microsoft Azure Timothy P. McAliley Microsoft Premier Field Engineer SQL Server

2

3 Agenda

4

5 Hybrid cloud solutions Geo-replication Restore to VM

6 Running SQL Server on an Microsoft Azure VM

7 Key Benefits

8 Key Benefits

9 Key Benefits

10 Easy on-ramp to cloud

11 Backup to Cloud

12 Key Concepts and Fun Facts Limitations Max Backup Size is 1TB Logical Device Name Not Supported Append To Existing Blob Not Supported Backups to Multiple Blobs in a Single Backup Operation Not Supported

13 Backup to Azure Backups CREATE CREDENTIAL mystoragecred WITH IDENTITY = mystorage', SECRET = <your storage access key> BACKUP DATABASE mydb TO URL =' WITH CREDENTIAL = mystoragecred', FORMAT, COMPRESSION, STATS = 5, MEDIANAME = mydb backup ', MEDIADESCRIPTION = 'Backup of mydb'

14 WA Box Windows Azure Blobs Backup to Windows Azure Windows Azure storage On-site/off-site storage costs Device management costs XDrives limited to 1 terabyte Max 16 drives Manage drives and policy Near bottomless storage Off-site, geo-redundant No provisioning No device management Media safety (decay-free) Remote accessibility

15 Backup to Windows Azure

16 Backup to Windows Azure Tool

17 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 Manage whole instance or particular databases Take advantage of backup to Azure Inherently off-site Geo-redundant Minimal storage costs Zero hardware management Example:

18 Benefits

19 Cloud DR

20 Hybrid cloud solutions

21 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 21

22 Typical Configuration 22

23 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 23

24 Inverse Deployment Configuration Supported 24

25 Technologies Supported Technology SQL Server Version Zero Data Loss Scope # Secondaries Automatic Failover Availability Groups Database Mirroring Log Shipping SQL Server 2012 SQL Server 2008 R2 SQL Server 2012 SQL Server 2008 R2 SQL Server 2012 Yes* (Sync Mode) Yes* (High Safety Mode) DB(s) 4 Yes (w/ additional cluster member)** DB 1 Yes (w/ Witness)** Readable Secondaries Yes Limited (database snapshots) No DB N No Limited (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 25

26 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 Requires: A solution for policy compliance Same Windows Domain Needs an Active Directory Domain Controller 26

27 Example of Availability Group Spanning On-premises and Windows Azure redmond.corp.microsoft.com Availability Group CSNB TA uswest.internal.cloudapp.net Virtual Network CSNB TA Windows Cluster VPN Device AGHybrid2 27

28 Architecture Diagram Cloud On-Premises Windows Cluster Availability Group Primary Secondary Secondary 28

29 Architecture Diagram Cloud On-Premises Windows Cluster Availability Group Primary Secondary Secondary 29

30 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) 30

31 Deploy DB to Microsoft Azure Wizard

32 Easy on-ramp to cloud

33 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-totransfer is database size

34 SQL Server Data & Log Files in Microsoft Azure Storage

35 SQL Server Data & Log Files in Microsoft 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

36 SQL Server Data & Log Files in Microsoft Azure Storage

37 References and Resources

38 References and Resources

39 Review and Summary

40 -Download SQL Server 2012 or SQL Server 2012 Evaluation Edition Call to action -Try Windows Azure

41 MCSE Data Platform Course Outline for MCSE: Data Platform

42 MCSE Business Intelligence Course Outline for MCSE: Business Intelligence

43 NETCOM ( )