The document describes Microsoft's Data Protection Manager (DPM) 2007 software. DPM 2007 provides continuous data protection, recovery, and archiving capabilities for Windows servers, applications, and files. It protects data through disk-based snapshots taken every 15 minutes, and can restore data to any point within the last 30 days. DPM 2007 integrates both disk-based and tape-based backup and supports recovery of Active Directory, SQL Server, Exchange and other Microsoft applications and file shares from a single tool.

3. DPM 2007 Continuous Data Protection for Windows Application and File Servers Rapid & Reliable Recovery from disk instead of tape Advanced 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 2003 Windows Server 2008 file shares and directories Windows XP Windows Vista

4. DPM Server Also available as a DPM OEM Appliance running on Windows Storage Server with integrated Disk & Tape DPM 2007 Active Directory® System State Windows Server 2003 Windows Server 2008 file shares and directories Enterprise DPML – “ Application Agent ” – per protected server Unified support of Microsoft applications SQL, Exchange, SharePoint, & Virtual Server – and files Protect DPM 2 DPM 4 DR – disaster recovery Bare Metal Recovery Pricing guidance posted on microsoft.com/DPM Standard DPML = “ File agent ” per protected server No additional “Open File” or add-on modules Windows XP Windows Vista

6. D:\ + \SQL_data + \Customer.MDF E:\ + \SQL_logs + \Customer.LDF

7. DPM Filter – Volume Map D:\ + \SQL_data + \Customer.MDF E:\ + \SQL_logs + \Customer.LDF

8. VOLUME (actual disk blocks) Time = 10:00 DPM Filter – Volume Map

9. DPM Filter – Volume Map Changed blocks noted File Write VOLUME (actual disk blocks) Time = 10:01

10. VOLUME (actual disk blocks) Time = 10:06 DPM Filter – Volume Map Changed blocks noted File Write VOLUME (actual disk blocks)

11. VOLUME (actual disk blocks) Time = 10:18 File Write DPM Filter – Volume Map Changed blocks noted

12. File Write Time = 10:26 DPM Filter – Volume Map Changed blocks noted VOLUME (actual disk blocks)

13. VSS Snapshot taken on production volume to ensure consistent data DPM Synchronization Time = 10:30 (up to every 30 minutes, usually daily) DPM Filter – Volume Map VOLUME (actual disk blocks)

14. 11 7 1 16 17 18 19 4 12 5 6 15 8 9 10 13 14 Block Order DPM Synchronization Time = 10:30 :01 VOLUME (actual disk blocks) VSS Snapshot taken on production volume to ensure consistent data Cache of changed blocks is sent to DPM server DPM Filter – Volume Map

15. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Time = 10:30 :02 VSS Snapshot taken on production volume to ensure consistent data Cache of changed blocks is sent to DPM server DPM Filter – Volume Map VOLUME (actual disk blocks) Transmit changed blocks from 10:00-10:30 to DPM server Data integrity preserved, since volume snapped Block Order

16. And File IO continues Time = 10:30 :03 VSS Snapshot taken on production volume to ensure consistent data Cache of changed blocks is sent to DPM server, while live disk continues. DPM Filter – Volume Map VOLUME (actual disk blocks) Transmit changed blocks from 10:00-10:30 to DPM server Data integrity preserved, since volume snapped 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Block Order

17. Time = 10:30 :04 VSS Snapshot taken on production volume to ensure consistent data Cache of changed blocks is sent to DPM server, while live disk continues. VSS snapshot released DPM Filter – Volume Map VOLUME (actual disk blocks) And File IO continues

22. DPM Replica Production Server

23. Baseline Initial Mirror DPM Replica Production Server

24. Every 15 minutes, closed transaction logs are sent to the DPM server DPM Replica 15 minute Syncs Production Server

25. Every 15 minutes, closed transaction logs are sent to the DPM server DPM Replica 15 minute Syncs Production Server

26. Every 15 minutes, closed transaction logs are sent to the DPM server DPM Replica 15 minute Syncs Production Server

27. DPM can restore server to any 15 minute point in time Database 0:00 Roll forward to 0:XX with transaction logs Restore DPM Replica Production Server

28. Express full At least weekly but usually daily, a DPM Express Full re-synchronizes the DPM Replica DPM Replica Production Server

29. Shadow Copy of 0:00 to 1:00 + Transaction logs Day 0 Usually daily, a DPM Express Full re-synchronizes the DPM Replica Express full DPM Replica Production Server

30. Day 1 : Data changes Shadow Copy of 0:00 to 1:00 + Transaction logs Day 0 15 minutes DPM Replica Production Server

31. Shadow Copy of 0:00 to 1:00 + Transaction logs Day 0 Day 1 : Data changes 15 minutes DPM Replica Production Server

32. Shadow Copy of 0:00 to 1:00 + Transaction logs Day 0 Day 1 : Data changes 15 minutes DPM Replica Production Server

33. DPM can restore to Today at 2:15 Use existing 1:00 replica Roll forward logs to 2:15 Shadow Copy of 0:00 to 1:00 + Transaction logs Day 0 DPM Replica Restore Production Server

34. DPM can restore to Yesterday at 10:45 Shadow copy 0:00 to rebuild day 0 Roll forward logs to yesterday at 10:45 Shadow Copy of 0:00 to 1:00 + Transaction logs Day 0 DPM Replica Restore Production Server

35. Database 1:00 Day 2 : Express Full - resynchronization Express Full Shadow Copy of 0:00 to 1:00 + Transaction logs Week 0 DPM Replica Production Server

36. Week 2 : Express Full - resynchronization DPM Replica Express Full Production Server

37. Up to 512 shadow copies, plus their logs w x 7d x 24h x 4 (15m) = 344,000 Recovery Points DPM Replica Production Server

41. SQL Primary DPM Database mirrored SQL cluster SQL Secondary

42. SQL Primary DPM Database mirrored SQL cluster SQL Secondary Service Pack 1

43. SQL Log Shipping SQL DPM

44. DPM MSCS SQL Cluster SQL Passive-node SQL Active-node

51. 100 GB 50 GB 40 GB 60 GB 100 GB Log Shipping 250GB of SQL databases For 2 weeks, 75GB x 14d = 1.05 TB On Local Disk SQL Server Local Disk (100+50+40+60) + (30+15+12+18) 325GB +100GB (log-shipped) 30 GB 15 GB 12 GB 18 GB Assume 70% Compression during backup 75 GB per backup

52. 100 GB 50 GB 40 GB 60 GB 100 GB Log Shipping 30 GB 15 GB 12 GB 18 GB 250GB of SQL databases On Local Disk Not needed – unless for Availability No local disk consumed with DPM 2007 SQL Server Local Disk (100+50+40+60) + (30+15+12+18) 250GB +100GB (log-shipped)

53. 100 GB 50 GB 40 GB 60 GB 250GB of SQL databases DPM Replica “ Express Full” Data Changes 250 GB DPM Replica

54. 100 GB 50 GB 40 GB 60 GB 250GB of SQL databases Assume 10% data change rate per day DPM Replica “ Express Full” 10 GB 5 GB 4 GB 6 GB 25 GB / day times 13 days For 2 weeks, 250 GB + 375 GB = 625 GB 250 GB DPM Replica 375 GB DPM recovery points

55. 100 GB 50 GB 40 GB 60 GB 250GB of SQL databases Assume 5 % data change rate per day DPM Replica “ Express Full” 5 GB 2½ GB 2 GB 3 GB 12½ GB / day times 13 days For 2 weeks, 250 GB + 168 GB = 418 GB 250 GB DPM Replica 168 GB DPM recovery points

56. 100 GB 50 GB 40 GB 60 GB 250GB of SQL databases Assume 5 % data change rate per day DPM Replica “ Express Full” 5 GB 2½ GB 2 GB 3 GB 12½ GB / day times 60 days For 2 months , 250 GB + 750 GB = 1 TB 250 GB DPM Replica 750 GB DPM recovery points

59. 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 2007 as their primary, and perhaps only, tool for managing backup and protection of SQL Server data .” For the entire SQL Server Magazine article, go to: http://www.sqlmag.com/Articles/ArticleID/97347/97347.htm

60. 4pp – Technical Overview 25pp – Implementation Whitepaper

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

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