【文章內(nèi)容簡介】 for requesting the copy and managing it once it’s been made. Improving Protection with System Center Data Protection Manager 2007When Microsoft introduced Data Protection Manager 2006 (DPM 2006), it targeted two key problem areas: the need for better backup and restore functionality with disk instead of tape and the need for better methods of centralizing remote and branch office backup. Although DPM 2006 is targeted primarily at protecting file servers and other servers running filebased applications, it’s still possible to use DPM 2006 to help protect SQL Server puters by using SQL Server Enterprise Manager to create a diskbased backup job to effectively dump the changed SQL data to a flat file on disk, and then protecting the resulting file using DPM 2006. Data Protection Manager (DPM) 2007 adds a high degree of application awareness, including the builtin ability to provide tailored, applicationaware protection for SQL Server, Exchange Server, and SharePoint Server. This application awareness is bined with a powerful user interface, plete PowerShell support, and a robust replication and checkpoint system that allows database administrators and IT generalists to perform their own backups and recoveries quickly and successfully.Expanded ProtectionDPM expands the basic data protection capabilities included in SQL Server by adding the ability to provide protection for selected databases with more granular control over your recovery time objective (RTO) and recovery point objective (RPO). Using only the tools provided with Windows Server and SQL Server, it is possible to take periodic full backups, but the frequency of these backups will vary according to the speed of your backup system and the amount of data you need to back up. The frequency at which you can create backups will control both the RPO and the RTO available to you. For example, with nightly tape backup, your RPO or “potential data loss” will be one business day, meaning that any server outage will likely cost up to an entire business day of data (and productivity) that will be unrecoverable. Meanwhile, your RTO, indicating how long it will actually take to recover, will vary according to the amount of data that has to be restored.By contrast, DPM can provide much more granular protection by bining SQL Server’s transaction log architecture with DPM’s blocklevel synchronization. After the initial baseline copy of the protected databases are on the DPM server, transaction logs can be continuously synchronized as often as every 15 minutes. DPM’s “express full” backup technology uses the SQL Server VSS writer to identify which database pages have changed on disk. Those pages, and only those pages, are copied to the DPM server, where they are stored as a set of differences from the preceding backup. DPM can maintain up to 512 of these differential backups. If you store one “express full” image per week plus the transaction logs every fifteen minutes in between, you end up with a total of more than 344,000 potential recovery points: 512 weekly images, each one of which has 7 (days) x 24 (hours) x 4 (15minute) transaction log targets. Each of these recovery points is guaranteed to be consistent and readable by SQL Server, and can be restored directly into the original database, to the same or a different SQL server, or to tape media.DPM further extends this protection by allowing you to seamlessly intermix disk and tape as recovery media. You can move your online snapshots to offline tape to provide much greater depths of protection。 in addition, you can schedule tapebased backup jobs to capture regular full backups to tape to meet your archiving and pliance needs while still preserving your ability to do finegrained 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。 if a recovery is required, the most recent DPM differential backup can be bined with the most recent set of transaction logs to provide rapid recovery to the desired RPO. Once the administrator chooses which pointintime recovery point to use for the restore, DPM assembles the necessary data from logs, differential backups, and full backups. This assembly process is pletely automatic and doesn’t require the administrator to be an expert in SQL Server database recovery. Similar protective methods are used to protect Exchange Server and SharePoint Server puters. Because DPM is aware of specific applications, it can tai