dpm.2007.for.sql sonvu

DPM 2007Continuous Data Protection for Windows Application and File ServersRapid & Reliable Recovery from disk instead of tapeAdvanced Technology for enterprises of all sizes

with integrated Disk & Tape

Up to Every 15 minutes

DPM 2007

Online Snapshots (up to 512)

Disk-based Recovery

Offline tape

Tape-based Archive

Active Directory®System State

Windows Server 2003Windows Server 2008 file shares and directories

Windows XPWindows Vista

Standard DPML = “File agent” per protected server

No additional “Open File” or add-on modules

DPM Server

Also available as a DPM OEM Appliancerunning on Windows Storage Server

with integrated Disk & TapeDPM 2007

Active Directory®System State

Windows Server 2003Windows Server 2008 file shares and directories

Windows XPWindows Vista

Enterprise DPML – “Application Agent” – per protected server

Unified support of Microsoft applications SQL, Exchange, SharePoint, & Virtual Server – and filesProtect DPM 2 DPM 4 DR – disaster recoveryBare Metal Recovery

Pricing guidance posted on microsoft.com/DPM

D:\ + \SQL_data + \Customer.MDF

E:\ + \SQL_logs + \Customer.LDF

DPM Filter – Volume Map

D:\ + \SQL_data + \Customer.MDF

E:\ + \SQL_logs + \Customer.LDF

VOLUME (actual disk blocks)

Time = 10:00


DPM Filter – Volume MapChanged blocks noted

File WriteFile Write


Time = 10:01


Time = 10:06


File WriteFile Write



Time = 10:18 File WriteFile Write


File WriteFile WriteTime = 10:26



1. VSS Snapshot taken on production volume to ensure consistent data

DPM SynchronizationDPM Synchronization

Time = 10:30 (up to every 30 minutes, usually daily)



111177111616171718181919441212556615158899101013131414Block OrderBlock Order

DPM SynchronizationDPM Synchronization

Time = 10:30:01



2. Cache of changed blocks is sent to DPM server


1122334455667788991010

1111

1212

1313

1414

1515

1616

1717

Time = 10:30:02


2. Cache of changed blocks is sent to DPM server



Transmit changed blocks from 10:00-10:30 to DPM serverData integrity preserved, since volume snapped


Block OrderBlock Order

And File IO continuesAnd File IO continues

Time = 10:30:03


2. Cache of changed blocks is sent to DPM server, while live disk continues.





1122334455667788991010

1111

1212

1313

1414

1515

1616

1717

Block OrderBlock Order

Time = 10:30:04


2. Cache of changed blocks is sent to DPM server, while live disk continues.

3. VSS snapshot released


VOLUME (actual disk blocks)And File IO continuesAnd File IO continues

DPM ReplicaProduction Server

Baseline Initial MirrorBaseline Initial MirrorBaseline Initial MirrorBaseline Initial Mirror


Every 15 minutes, closed transaction logs are sent to the DPM server

DPM Replica

15 minute Syncs15 minute Syncs15 minute Syncs15 minute Syncs

Production Server

DPM can restore server to any 15 minute point in time Database 0:00 Roll forward to 0:XX with transaction logs

RestoreRestoreRestoreRestore


Express fullExpress fullExpress fullExpress full

At least weekly but usually daily, a DPM Express Full re-synchronizes the DPM Replica


Shadow Copyof 0:00 to 1:00

+Transaction logs

Day 0Usually daily, a DPM Express Full re-synchronizes the DPM Replica

Express fullExpress fullExpress fullExpress full


Day 1 : Data changes


+Transaction logs

Day 0

15 minutes15 minutes15 minutes15 minutes



+Transaction logs

Day 0Day 1 : Data changes

15 minutes15 minutes15 minutes15 minutes


DPM can restore to Today at 2:15

Use existing 1:00 replicaRoll forward logs to 2:15


+Transaction logs

Day 0

DPM Replica


Production Server

DPM can restore to Yesterday at 10:45

Shadow copy 0:00 to rebuild day 0Roll forward logs to yesterday at 10:45


+Transaction logs

Day 0

DPM Replica


Production Server

DatabaseDatabase

1:00DatabaseDatabase

1:00

Day 2 : Express Full - resynchronization

Express FullExpress FullExpress FullExpress Full


+Transaction logs

Week 0


Week 2 : Express Full - resynchronization

DPM Replica

Express FullExpress FullExpress FullExpress Full

Production Server

Up to 512 shadow copies, plus their logs

512w x 7d x 24h x 4(15m) = 344,000 Recovery Points


SQLPrimary

DPM

Database mirrored SQL cluster

SQLSecondary

SQLPrimary

DPM

Database mirrored SQL cluster

SQLSecondary

Service Pack 1Service Pack 1

SQL Log Shipping

SQL

DPM

DPM

MSCS SQL Cluster

SQLPassive-node

SQLActive-node

100 GB 50 GB 40 GB 60 GB100 GBLog

Shipping

30 GB 15 GB 12 GB 18 GBAssume 70%Assume 70%CompressionCompression

during backupduring backup

250GB of SQL databases250GB of SQL databases

75 GBper backup For 2 weeks,For 2 weeks,

75GB x 14d =75GB x 14d =1.05 TB1.05 TB

On On Local DiskLocal Disk

SQL Server Local DiskSQL Server Local Disk(100+50+40+60) + (100+50+40+60) +

(30+15+12+18) (30+15+12+18) 325GB 325GB +100GB+100GB(log-shipped)(log-shipped)

100 GB 50 GB 40 GB 60 GB100 GBLog

Shipping

30 GB 15 GB 12 GB 18 GB


On On Local DiskLocal Disk

Not needed – unless for Availability

No local disk consumed

with DPM 2007

SQL Server Local DiskSQL Server Local Disk(100+50+40+60) + (100+50+40+60) +

(30+15+12+18) (30+15+12+18) 250GB250GB +100GB+100GB(log-shipped)(log-shipped)

100 GB 50 GB 40 GB 60 GB


250 GBDPM Replica

DPM ReplicaDPM Replica““Express Express

Full”Full”

Data Data ChangesChanges

100 GB 50 GB 40 GB 60 GB


250 GBDPM Replica

Assume 10% data Assume 10% data change rate per daychange rate per day


Full”Full”

10 GB 5 GB 4 GB 6 GB

375 GBDPM recovery

points

25 GB / day25 GB / daytimes 13 times 13 daysdays

For 2 weeks, 250 GB + 375 GB = For 2 weeks, 250 GB + 375 GB = 625 625 GBGB

100 GB 50 GB 40 GB 60 GB


250 GBDPM Replica

Assume Assume 55%% data data change rate per daychange rate per day


Full”Full”

5 GB 2½ GB 2 GB 3 GB

168 GBDPM recovery

points

12½ GB / 12½ GB / daydaytimes 13 times 13 daysdaysFor 2 weeks, 250 GB + 168 GB = For 2 weeks, 250 GB + 168 GB = 418 418

GBGB

100 GB 50 GB 40 GB 60 GB


250 GBDPM Replica

Assume Assume 55%% data data change rate per daychange rate per day


Full”Full”

5 GB 2½ GB 2 GB 3 GB

750 GBDPM recovery

points

12½ GB / 12½ GB / daydaytimes 60 times 60 daysdaysFor For 2 months2 months, 250 GB + 750 GB = , 250 GB + 750 GB = 1 TB1 TB

Brian Moran, SQL Server MVP & SQL Server Magazine writer had this to say:

“I love the fact DPM 2007 inherently understands all of the core server technologies in the Microsoft arsenal. It's nice that an administrator can use a single tool to protect data. It's even lovelier that DPM 2007 supports the ability to treat data from different sources as part as the same "protection group." For example, if my accounting team uses SharePoint, OS files, and SQL Server databases as part of their core functionality, and I want to restore my "accounting team" to a single consistent point in time, DPM 2007 can handle that for me. That's sweet.”

“Historically, most enterprise and midmarket customers have had to rely on several third-party offerings to manage their SQL Server backup infrastructure. Historically, backup hasn't really been seen as the cool and sexy part of database management, not that the outside world considers database management to be hot and sexy to begin with. I think the current iteration of DPM 2007 is a large upgrade in functionality from prior Microsoft offerings.

Realistically, many SQL Server customers will be able to standardize on DPM Realistically, many SQL Server customers will be able to standardize on DPM 2007 as their primary, and perhaps only, tool for managing backup and 2007 as their primary, and perhaps only, tool for managing backup and protection of SQL Server dataprotection of SQL Server data.”

For the entire SQL Server Magazine article, go to: http://www.sqlmag.com/Articles/ArticleID/97347/97347.htm

4pp – Technical Overview 25pp – Implementation Whitepaper

SQL Server plus DPM 2007 – attach guidance (partner version available)

© 2008 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.