Selecting Protection Group Members
適用対象: System Center Data Protection Manager 2010
With System Center Data Protection Manager (DPM) 2010, there are several approaches you can take to organize data sources into protection groups, including the following:
By computer, with all data sources for a computer belonging to the same protection group.
An advantage of this approach is that with all data from a computer in the same protection group, you have a single point of adjustment for performance loads.
A constraint of this approach is that all data sources of a type on that computer must be assigned the same recovery goals.
By data type, separating files and each application data type into different protection groups.
An advantage of this approach is that you can manage data types as a group.
A constraint of this approach is that recovering a server can require multiple tapes from several protection groups.
By definition, all members of a protection group share recovery goals—that is, all data sources of a type in a protection group must have the same retention range and data loss tolerance.
If you have only a single stand-alone tape, use a single protection group to minimize the effort to change tapes. Multiple protection groups require a separate tape for each protection group.
Guidelines for Protection Groups
As you design the structure of your protection groups, keep the following guidelines and restrictions in mind:
Data sources on a computer must be protected by the same DPM server. In DPM, a data source is a volume, share, database, or storage group that is a member of a protection group.
You can include data sources from more than one computer in a protection group.
When you select a parent folder or share, its subfolders are automatically selected. You can designate subfolders for exclusion and also exclude file types by extension.
Verify that you do not have more than 100 protectable data sources on a single volume. If you do, distribute your data sources across more volumes if possible.
All protection group members of the same type (file or application data) will have the same recovery goals. However, within the same protection group, files can have different recovery goals than application data.
Exception: If a SQL Server database is configured to use the Simple Recovery Model or is the primary database in a log shipping pair, the recovery goals for that database will be configured separately from the recovery goals for all other application data.
All storage groups on a computer running Exchange Server 2003 must be members of the same protection group.
When you select a data source that contains a reparse point (mount points and junction points are data sources that contain reparse points), DPM prompts you to specify whether you want to include the target of the reparse point in the protection group. The reparse point itself is not replicated; you must manually re-create the reparse point when you recover the data.
Special Considerations for Protecting Data on Workstations
Your recovery goals for data on user workstations might differ from the recovery goals for data on file servers. You should consider placing file servers and workstations in different protection groups so that you can adjust the synchronization schedules separately. For example, if you synchronize data on file servers every 15 minutes, any workstations that belong to the same protection group as the file servers are also synchronized every 15 minutes.
Special Considerations for Protecting Data Over a WAN
Network bandwidth usage throttling and on-the-wire compression are performance optimization features that are particularly important for deployments in which a DPM server protects data over a wide area network (WAN) or other slow network.
On-the-wire compression is configured at the protection-group level.
Network bandwidth usage throttling is configured at the protected-computer level. In addition, you can specify different network bandwidth usage throttling rates for work hours, non-work hours, and weekends, and you define the times for each of those categories.
When protecting application data such as Exchange storage groups or SQL Server databases over a WAN, consider reducing the schedule for express full backups.
How Important Is the Protection Group Membership Decision?
Protection group members cannot be moved between protection groups. If you decide later that a protection group member needs to be in a different protection group, you must remove the member from its protection group and then add it to a different protection group.
If you determine that the members of a protection group no longer require protection, you can stop protection of the protection group. When you stop protection, your options are to retain protected data or to delete protected data.
Retain protected data option: Retains the replica on disk with associated recovery points and tapes for the specified retention range.
Delete protected data option: Deletes the replica on disk and expires data on the tapes.