Meet Xin Jin| @xijin

Program manager, SQL Server, Microsoft

Drove the delivery of Backup to URL and Managed Backup as a key hybrid feature in SQL 2014. Led the performance work stream of SQL Server in Windows Azure Virtual Machine

Also had worked on backup service in the Windows Azure SQL Database, service health and resource management in multitenancy environment, database consolidation and virtualization in private cloud , etc.

Meet George Li | @like

Program Manager, Microsoft
Drove the release of the AMR Tool for IM OLTP Produced guidance for using IM OLTP on Azure VMs Drove the release of the SQL Server Backup to Azure Tool

Course Topics
Getting Started with PowerShell
01 | Backup to URL in SQL 2012 & 2014 02 | Backup to Windows Azure Tool 03 | Managed Backup to Windows Azure

Setting Expectations
Target Audience
IT Pros Customers already using Windows Azure Virtual Machines

Suggested Prerequisites/Supporting Material

Backup to URL in SQL 2012

Join the MVA Community!

Microsoft Virtual Academy
Free online learning tailored for IT Pros and Developers Over 1M registered users Up-to-date, relevant training on variety of Microsoft products

Earnwhileyoulearn!
Get 50 MVA Points for this event! Visit http://aka.ms/MVA-Voucher Enter this code: PltfmSQL (expires 1/5/2014)

01 | Backup to Cloud
Xin Jin| Program Manager George Li| Program Manager

Backup to URL (SQL2012/SQL2014)

Windows Azure Storage Near bottomless storage Off-site, geo-redundant No provisioning No device management Media safety (decay free) Remote accessibility

Windows Azure VM

On-premise box

using Microsoft.SqlServer.Management.Smo; CREATE CREDENTIAL mystoragecred $url = "https://[storage].blob.core.windows.net/backups/db.bak" WITH IDENTITY = mystorage', $credential = "mycredential" SECRET = <your storage access key> $server = "SQLSERVER:\SQL\[computer]\DEFAULT" Backup mybackup = new Backup(); BACKUP DATABASE mydb TO URL ='https://mystorage.blob.core.windows.net/backupCD $server mybackup.CredentialName = strCredential; container/mydb-20130411.bak' Backup-SqlDatabase -Database AdventureWorks2012 mybackup.Database strDatabase; WITH CREDENTIAL = = mystoragecred', mybackup.CompressionOption = 5, BackupCompressionOptions.On; FORMAT, COMPRESSION, STATS -backupFile $url mybackup.Devices.AddDevice(desturl, MEDIANAME = mydb backup 20130411', DeviceType.Url); MEDIADESCRIPTION = 'Backup of mydb' -SqlCredential $credential -CompressionOption On mybackup.SqlBackup(myLocalServer);

Backup To URL Perf vs Latency chart

Backup and restore times are proportional to bandwidth Backup times fairly constant up to 1000ms latency Restore times proportional to latency

Example Backup Size is: 138215424 (131.8MB)

02 | Backup to Windows Azure Tool

Backup to Windows Azure Tool

Stand-alone Tool that adds backup to Windows Azure capabilities and backup encryption to prior
versions of SQL Server

One Cloud Backup strategy across prior

versions of SQL Server including 2005, 2008, and 2008 R2 locally or in the cloud

Adds backup encryption to prior versions,

Takes advantage of backup to Azure

Easy configuration
http://www.microsoft.com/enus/download/details.aspx?id=40740

03 | Managed Backup to Windows Azure

Managed Backup to Windows Azure

What does it deliver
An agent that manages and automates SQL Server backup policy

Main benefits
Flexibility in configuration and no need to manage backup policy

Minimal knobs Context-aware e.g. workload/throttling Manage whole instance, or particular DBs Container & file naming, backup jobs Retention User action detection Example: EXEC smart_admin.sp_set_db_backup @database_name='TestDB', @retention_days=30, @credential_name='MyCredential', @encryption_algorithm='NO_ENCRYPTION', @enable_backup=1 GO

Intelligence built-in

Leverage Backup to Azure

Inherently off-site & geo-redundant Minimal storage costs Zero hardware management

Benefits
Built-in and automated backup offers lower management/operating costs

Peace of mind - No need to manage backup policy Intelligence

Leverage the near bottomless, highly redundant storage of Windows Azure

Allows for large scale management No device provisioning/management (Zero hardware management) Lower storage costs

Built-in Intelligence 1) Main loop

Not merely time/frequency-based (E.g. Maintenance Plan) Skips unnecessary (log) backups when no DB activity Throttle
Cap the full database backups that can be issued by the main loop simultaneously. Stagger log backups
(i) Log accumulation based - exceeds 5MB. (ii) at regular intervals.
DB ID= x

1. Is SB on for DB? Yes 2. Is backup chain broken? No 3. Is DB backup due? No

No DB ID++

Yes 5. Schedule DB backup

Yes

4. Is log backup due?

Yes

5. Schedule Log Backup

No

Built-in Intelligence 2) File Retention

Min: 1 day; Max: 30 days Periodically loops over the list of databases, checks corresponding WA Storage, and looks for files that are out of retention period. Takes into account the various fork paths and keeps the necessary files to guarantee restorability in the retention time frame.

V1 Limitations
Only supports Windows Azure storage as destination for backups - No local disks Database backups & T-log backups No differential backups Backup of system databases not supported Recovery Models: Only databases set to Full or Bulk-logged model are supported. Databases set to simple recovery model not supported. No support for log shipping Database Mirroring: supported only on the principal database. AlwaysOn: support all-in the cloud config Bydesign:Conflictwithotherbackupsolutionssidebyside(DPM,) Limited user action detection and mitigation

Key Takeaways
Backup to URL in SQL 2012/2014
T-SQL, Powershell, SMO, UI (Backup/Restore, Maintenance Plan)

Backup to Cloud tool

Local or WA storage (SQL prior to 2012)

Managed Backup to Windows Azure

Automates backup managements

2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics 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.