Learn. Connect. Explore.Learn. Connect. Explore.

Be Smart with Smart Backup

Pranab Mazumdar

Escalation Engineer – Data Platform Services (GBS)

Agenda..The Problem Statement

Smart Backup

Architecture

Important

Consideration.

Problem…???

•Database Corruption, Data

Loss … DR Strategy

•Performance Issue.. Database

Maintenance

•Consistency Checks.

Smart Backup

Automated Backup of

databases at regular

intervals to Windows

Azure Blob Storage

Backup intervals are

based on

Configuration & in-

built intelligence

A new subsystem

AutoAdmin has been

introduced inside

SQL Server Agent

Uses Backup To Url

feature introduced in

SQL Server 2012

Uses Backup

Encryption feature

introduced in SQL

Server 2014

Compatible with SQL

data files on Blob

Store

Flexible , reliable ,

limitless , Cost-effective

& Secured off-site

archive option

Provides instant , highly

available and a durable

archiving option

Backup files stored on

Windows Azure

hardware with geo

replication

DB backups can be

restored back to

windows Azure VMs or

on premise SQL Server

Instances

Just provide the

Backup File

retention period &

location… SQL

takes care of the

rest

Back-Up to the Cloud

Key Benefits

Reduce CAPEX & OPEX

Improve Data Security

Restore Backup to Azure VM

Full SQL Server Backup

Windows Azure

Storage

Geo replication

Restore to VM

On-premise network

SQL Server

Full data encryptionPeriodic Snapshot

(automatic/manual)

Supported Interface..

Enterprise, Business Intelligence, Standard and Web Editions support

this feature System SPs for enabling, configuring, and monitoring Smart Backup.

NO GUI Support enabling or Configuring.

TSQL Main Interface to interact with Smart Backup

System Functions to retrieve Config settings, Parameter Values, Backup

location.

XEVent Interface Available to Log Errors / Warnings and Alert

Mechanism.

SQ

L A

gen

t Exe

SQL Agent Subsystem

(SQLAAMSS.DLL )

Smart Admin Manager

(Microsoft.SqlAutoAdmin.SqlAutoAdmin.dl

l)

Smart Backup Task Agent Microsoft.SqlAutoAdmin.AutoBackupAgen

t.dll

Smart **** Task Agent Microsoft.SqlAutoAdmin.Auto***Agent.dll

Smart **** Task Agent Microsoft.SqlAutoAdmin.Auto****Agent.dll

New Code VNext

Interface /Subsystem

between SQL Agent and

Smart Admin feature.

Smart Admin Manager • Task agent loading and unloading

• Provides Services to task Agent

Logging, Metadata Storage,

Scheduling etc.

• Smart Admin Job Execution.

Auto Admin Architecture…

DEMO

Caveats and Coexistence

Only Full & Tlog backup

to begin with

Only backup to Azure

Blob Storage in this

release

Max File Size of a

backup is 1TB, By

default uses

compression during

backup

Database has to be in

an Online state for

backup to be

considered

Always on support only

on Windows Azure VMs

, For DBM mirror dbs

will be skipped

System databases are

not considered ,

Databases with simple

recovery model are not

considered

Important Considerations..

If DB is detached , renamed

or dropped,

previous backups will

remain till retention period

If you change the Recovery

Model from Simple to Full,

Smart Backup has to be

manually enabled for the

DB

Full database backups:

1 week since last full

backup

or log growth exceeds 1 GB

or log chain is broken

Transaction Log backups:

Log >= 5 MB or more,

or 2 hours since last log

backup

Only 10 concurrent Full

Backups can be executed at

a time

Maintenance Plan ,

Logshipping & Ad Hoc

Backups breaks Tlog chain

consider using with

copy_only option

Backup Trigger Point• Smart Backup enabled the first time, or when Smart Backup 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.

FULL

Backup

• No log backup history that can be found, Usually true the first time Smart Backup is enabled.

• The transaction log space used is 5 MB or larger.

• The Log space used percentage is more than 50%.

• 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.

TLOG

Backup

Take Aways…

Smart Backup

is available in

Both On-

premise and

Windows

Azure VMs

SQL Server

Manages

database

backups

without any

manual

intervention

Database

Administrators

can

concentrate

on more

important

activities

Backups are

Automatically

stored in a

offsite Secured

Environment

References• Related references for you to expand your knowledge on the subject

• <Quote related references here>

technet.microsoft.com/en-in

aka.ms/mva

msdn.microsoft.com/

Tell us what you think

Scan the QR code to evaluate

this session.

< QR Code will be given a week before

Tech Ed >

Follow us online

Facebookfacebook.com/MicrosoftDeveloper.India

twitter.com/msdevindia

Twitter

Twitter: PranabM37

Email:PRANABM@Microsoft.com