1. Server & Tools Business
9/12/2018
Cloud Backup
<Speaker Name> | <Speaker Title>
PPE Application and Data Platform | <Month Date, Year>
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

2. 01 | Backing up to a URL in SQL Server 2012 and SQL Server 2014

3. Backing up to a URL SQL Server 2012 and SQL Server 2014
Windows Azure storage
Windows Azure virtual machine
On-premises box
Near-bottomless storage
Off-site, geo-redundant
No provisioning
No device management
Media safety (decay free)
Remote accessibility
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'
$url = "
$credential = "mycredential"
$server = "SQLSERVER:\SQL\[computer]\DEFAULT"
CD $server
Backup-SqlDatabase -Database AdventureWorks2012
-backupFile $url
-SqlCredential $credential -CompressionOption On
using Microsoft.SqlServer.Management.Smo; …
Backup mybackup = new Backup();
mybackup.CredentialName = strCredential;
mybackup.Database = strDatabase;
mybackup.CompressionOption = BackupCompressionOptions.On;
mybackup.Devices.AddDevice(desturl, DeviceType.Url);
mybackup.SqlBackup(myLocalServer);

4. Backing up to a URL Performance versus latency chart
Backup and restore times are proportional to bandwidth
Backup times are fairly constant up to 1000 ms latency
Restore times are proportional to latency
Why backup to cloud?
Box
Onsite / offsite storage cost Lack of flexibility
Device management cost
Windows Azure Virtual Machine
XDrives limited to 1TB
Attach max of 16 Drives
Have to manage drives, develop & maintain backup policy
Why not backup to cloud?
Network limitations – upload/download, proxy restrictions
File size – 1TB upper limit, practical limits determined by network
Security/compliance concerns with offsite storage
Example backup size: 138,215,424 (131.8 MB)

5. User Interface for Backup and Restore for a URL
Server & Tools Business
9/12/2018
User Interface for Backup and Restore for a URL
Demo
See MVA recording for demonstration.
Refer to “PPE Day 1 and 2 SQL Server 2014 Demo Guide.docx” – see “Backup to Cloud – Manual with Encryption” demo on page 53.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

6. 02 | Backing Up Through Windows Azure Tool

7. Backing Up Through Windows Azure Tool
Windows Azure Tool is a standalone tool that adds backup capabilities to Windows Azure and backup encryption to previous versions of SQL Server
Benefits
Offers one-cloud backup strategy across previous versions of SQL Server, including 2005, 2008, and R2
Adds backup encryption to previous versions, locally or in the cloud
Takes advantage of backup to Windows Azure
Easier to configure

8. Backing Up Through Windows Azure Tool
Server & Tools Business
9/12/2018
Backing Up Through Windows Azure Tool
Demo
See MVA recording for demonstration.
Refer to “PPE Day 1 and 2 SQL Server 2014 Demo Guide.docx” – see “Backup to Cloud – Support for Previous Versions of SQL Server” on page 59.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

9. 03 | Managed Backup to Windows Azure

10. Managed backup to Windows Azure
Managed backup delivers an agent that manages and automates SQL Server backup policy
Benefits
Flexibility in configuration and no need to manage backup policy
Minimal knobs
Context-aware—workload and throttling
Manage whole instances or particular databases
Built-in intelligence
Container and file naming, backup jobs
Retention
Detection of user action
Uses back up to Windows Azure
Inherently offsite and geographically redundant
Minimal storage costs
Zero hardware management
Example
EXEC smart_admin.sp_set_db_backup GO

11. Managed backup to Windows Azure benefits (Continued)
Lower management and operating costs through built-in and automated backup
Peace of mind—no need to manage backup policy
Intelligence
Gains leverage from the nearly bottomless, highly redundant storage of Windows Azure
Allows for large-scale management
No device provisioning and management (virtually no hardware management)
Lower storage costs
* Working with marketing team to build out a couple of sample scenarios that can be used by the Azure field to talk through backup storage sizing and cost with a customer.
(along with patching and other administration solutions in future)

12. Built-in intelligence Main loop
2. Is backup chain broken?
Yes No
5. Schedule log backup
4. Is log backup due?
3. Is DB backup due?
DB ID++
1. Is SB on for DB?
DB ID= x
5. Schedule DB backup
Not based on time and frequency (for example, maintenance plan)
Skips unnecessary (log) backups when there is no database activity
Throttle
Caps the full database backups that can be issued by the main loop simultaneously.
Staggers log backups
Based on log accumulation—exceeds 5 megabytes
Occurs at regular intervals
Full Database Backup: SQL Server Managed Backup to Windows Azure agent schedules a full database backup if any of the following is true.
A database is SQL Server Managed Backup to Windows Azure enabled for the first time, or when SQL Server Managed Backup to Windows Azure is enabled with default settings at the instance level.
The log growth since last full database backup is equal to or larger than 1 GB.
The maximum time interval of one week has passed since the last full database backup.
The log chain is broken. SQL Server Managed Backup to Windows Azure periodically checks to see whether the log chain is intact by comparing the first and last LSNs of the backup files. If there is break in the log chain for any reason, SQL Server Managed Backup to Windows Azure schedules a full database backup. The most common reason for log chain breaks is probably a backup command issued using Transact-SQL or through the Backup task in SQL Server Management Studio. Other common scenarios include accidental deletion of the backup log files, or accidental overwrites of backups.
Transaction Log Backup: SQL Server Managed Backup to Windows Azure schedules a log backup if any of the following is true:
There is no log backup history that can be found. This is usually true when SQL Server Managed Backup to Windows Azure is enabled for the first time.
The transaction log space used is 5 MB or larger.
The maximum time interval of 2 hours since the last log backup is reached.
Any time the transaction log backup is lagging behind a full database backup. The goal is to keep the log chain ahead of full backup.

13. Built-in intelligence File retention
Minimum is one day; maximum is 30 days
Periodically loops over the list of databases, checks corresponding Windows Azure storage, and looks for files that are out of the retention period
Takes into account the various fork paths and keeps the necessary files to guarantee restorability in the retention time frame

14. Managed Backup to Windows Azure
Server & Tools Business
9/12/2018
Managed Backup to Windows Azure
Demo
See MVA recording for demonstration.
Refer to “PPE Day 1 and 2 SQL Server 2014 Demo Guide.docx” – “Backup to Cloud – Managed” demo on page 57.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

15. V1 limitations
Only supports Windows Azure storage as a destination for backups—no local disks
Database backups and T-log backups—no differential backups
Does not support backup of system databases
Recovery models: Supports only databases set to full or bulk-logged model; does not support databases set to simple recovery model
No support for log shipping
Supports database mirroring only in the principal database
AlwaysOn: Supports all (in the cloud configuration)
By design: Conflicts with other backup solutions side by side (such as DPM)
Detects and mitigates limited user actions
Smart Backup does not support System databases. At one point was evaluating msdb.
- Error handling needed
- Testing needed - case with long recovery of msdb.
- Doc requirement – During the restore of msdb, SQL Agent needs to be stopped

16. Key takeaways Backup to URL in SQL Server 2012 and SQL Server 2014
T-SQL, Windows PowerShell, Server Management Objects, UI (backup and restore, maintenance plan)
Backup to cloud tool
Storage locally or in Windows Azure (SQL Server versions prior to 2012)
Managed backup to Windows Azure
Automates management of backups

17. ESP Sales Presentation for Mobility
4/10/2013
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Azure 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
Microsoft Corporation