【正文】 ined restores at high speed directly from disk. In addition to directly restoring individual protected databases, you can also use DPM to capture system state data so that you can restore an entire protected server. These restores can use any of the past iterations of data you’ve chosen to capture on the DPM server or on an attached tape system, again giving you excellent granularity for recovery bined with short restore periods and fast restore speeds.Application AwarenessMany existing backup solutions offer generic backup services that can sometimes be adapted to various applications. Instead of adopting this model, DPM 2007 takes advantage of three fully supported Microsoft technologies to provide continuous data protection specifically for SQL Server:? The DPM blockbased replication engine is used to make the initial copy of a protected database, ensuring a plete and consistent copy is made. DPM’s network transport ensures that the copied data is delivered intact to the DPM server.? After the initial copy is made, DPM captures “express full” backups using the SQL Server VSS writer, which identifies which blocks have changed in the protected database. Only those blocks (or fragments) are sent to the DPM server for protection. By storing only the differences between individual express full backups, DPM is able to maintain up to 512 shadow copies of the full data set. ? In between express full copy captures, the standard SQL Server transaction logging mechanism is used to offer uptotheminute protection. The log files themselves are replicated by DPM。 System Center Data Protection Manager (DPM) 2007 extends the native SQL Server feature set to provide continuous data protection with bytelevel replication and integrity checking, plus full support for disktodisk and disktodisktotape backup. DPM 2007 offers prehensive data protection for organizations of all sizes, helping to maintain the business value of your SQL Server infrastructure with enhanced protection making it more available.The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a mitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.ContentsContents 3Protecting Your Critical Business Data 4The Business Case for Better Protection 4Technical Obstacles to Effective Data Protection 5Tape System Efficiency, Robustness, and Cost 5Network Bandwidth, Latency, and Usage 5Application Awareness and Support 6Improving Protection with System Center Data Protection Manager 2007 6Expanded Protection 6Application Awareness 7Seamless Disk and TapeBased Recovery 7Ease of Use and Management 8Using Microsoft DPM to Protect Microsoft SQL Server 8Deploying DPM to Protect SQL Servers 9Installing the DPM Server 9Allocating Storage on the DPM Server 9Installing the DPM Agent on SQL Server Computers 10Creating and Configuring Protection Groups 11Additional Considerations 13Creating the Protection Group 13Recovering SQL Server Databases 16Recovering a Database to its Original Location 16Recovering a Renamed Copy of a Database 18Recovering a Database to a Network Folder 18Recovering a Copy of the Database to Tape 19Conclusion 20Related Links 21Protecting Your Critical Business DataBusinesses of all sizes increasingly find themselves in a difficult position: they need better protection for their critical data, but they need to get that protection while meeting a host of constraints, including requirements for pliance, auditing, and IT overhead cost reduction. Meeting these challenges begins with understanding the real business case for improved data protection, then identifying the technical obstacles to implementing improved protection.The Business Case for Better ProtectionMagnetic tape has long been the primary means of system backup and recovery. The tape systems in mon use today share many of the same basic technologies as the first magnetic wire recording systems invented more than 50 years ago. While tapebased backup systems offer advantages for some recovery goals, tape as a recovery medium is being less and less suitable because of five factors that have emerged as trends in data protection and recovery:? Downtime costs more. As more and more businesses e to depend absolutely on their information systems, the cost of outages and failures continues to increase. Many panies suffer direct financial losses as the result of downtime that degrades their ability to carry out normal business operations, while others incur costs related to lost productivity, missed opportunities, and damaged reputations. As the time pressures on business operations continue to grow, downtime will continue to bee increasingly expensive.? Tapebased restores