【正文】 ection Manager 2007 Deployment Guide for instructions about installing protection agents. To install the DPM protection agent on a SQL Server puter, do the following:1. Open DPM Administrator Console (Start, All Programs, Microsoft System Center Data Protection Manager), click Management on the navigation bar, and click the Agents tab. In the Actions pane, click Install. The Install Agents Wizard appears.2. The first time you use the wizard, DPM assembles a list of potential servers from Active Directory. The daily autodiscovery process creates a stored list of servers that is used for subsequent installations. Select up to 50 servers and click Add. You can also specify a server by typing its name in the Server name box and clicking Add. When you are finished adding servers, click Next. (See Figure 3.) In the final release of DPM 2007, administrators will also have the option of deploying the DPM agent via Active Directory174。 the protection software is responsible 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。 the electromechanical ponents that physically move the tape are prone to failure at higher rates than solidstate ponents. The tapes themselves are subject to physical wear and must be stored and maintained in the right environmental conditions to remain usable. This reality is often underappreciated when one is relying on longterm viability of data.? Tapebased systems don’t provide an effective means of centralizing backup and restore processes. Most tapebased backup solutions require either a hefty allocation of bandwidth between a remote site and the central backup site or a local tape drive at the remote site, which then introduces the problem of how media are managed, cataloged, and stored between the remote and central sites. ? Tape systems have historically been poorly integrated with diskbased backup systems. Companies seeking to bine the high performance and robustness of diskbased backup with the low longterm storage costs of tape solutions have frequently found that bining systems from multiple vendors gives them all the drawbacks of both methods. In consideration of these constraints, more and more panies are recognizing that tape is not a preferable medium for routine data recovery, but is best served for longterm data retention and archival where disk may not be as practical.Network Bandwidth, Latency, and UsageBackup systems operate by making a faithful copy of