Less complicated point-in-time restoration Point-in-time (PIT) restoration – from a lagged database copy requires an administrator to perform a complex operation that involves locating and replaying specific log files as part of the recovery process. DPM allows administrators to perform PIT recovery with several quick selections from an intuitive GUI interface. The interface minimizes the complexity and time required for a PIT restoration, ensuring that the appropriate data is reliably restored. Fewer Exchange servers are needed - Leveraging DAGs to provide a comprehensive data protection solution requires that you deploy a large number of Exchange Servers. For example, to provide a mailbox database copy that allows for automatic failover and another that allows for a point-in-time (PIT) restore, you will need to deploy a minimum of three Exchange mailbox servers: One to host the active mailbox database, one to host the up-to-date copy, and one to host the lagged copy. If you are attempting to also provide offsite backup and recovery, even more Exchange mailbox servers are required. A robust data protection solution that relies solely on DAGs will require a significant investment in Exchange Server 2010 licenses. With a DPM solution in place, offsite backup and PIT restores can be handled through DPM with DAGs implemented primarily as a high availability solution. A DPM solution minimizes the complexity of the Exchange infrastructure, and licensing a DPM server is more cost- effective than licensing the necessary extra instances of Exchange. Longer retention range - DAG lagged copies offer administrators limited PIT recovery options. By design, PIT recovery from a lagged recovery is limited to a maximum of 14 days. PIT recovery of data protected by DPM 2010 enhances the data protection available to administrators by providing PIT restore from outside the DAG14-day limitation. More consistent backup and recovery process - DPM 2010 allows an organization to use a consistent backup and recovery process across multiple workloads such as File servers, SQL, Hyper-V, and SharePoint. DPM 2010 and other Exchange Roles When protecting Exchange Server 2010, administrators must consider how other Exchange Server roles such as the Hub Transport and Client Access Server should be
Less complicated point-in-time restoration – Point-in-time (PIT) restoration from a lagged database copy requires an administrator to perform a complex operation that involves locating and replaying specific log files as part of the recovery process. DPM allows administrators to perform PIT recovery with several quick selections from an intuitive GUI interface. The interface minimizes the complexity and time required for a PIT restoration, ensuring that the appropriate data is reliably restored. Fewer Exchange servers are needed - Leveraging DAGs to provide a comprehensive data protection solution requires that you deploy a large number of Exchange Servers. For example, to provide a mailbox database copy that allows for automatic failover and another that allows for a point-in-time (PIT) restore, you will need to deploy a minimum of three Exchange mailbox servers: One to host the active mailbox database, one to host the up-to-date copy, and one to host the lagged copy. If you are attempting to also provide offsite backup and recovery, even more Exchange mailbox servers are required. A robust data protection solution that relies solely on DAGs will require a significant investment in Exchange Server 2010 licenses. With a DPM solution in place, offsite backup and PIT restores can be handled through DPM with DAGs implemented primarily as a high availability solution. A DPM solution minimizes the complexity of the Exchange infrastructure, and licensing a DPM server is more cost- effective than licensing the necessary extra instances of Exchange. Longer retention range - DAG lagged copies offer administrators limited PIT recovery options. By design, PIT recovery from a lagged recovery is limited to a maximum of 14 days. PIT recovery of data protected by DPM 2010 enhances the data protection available to administrators by providing PIT restore from outside the DAG14-day limitation. More consistent backup and recovery process - DPM 2010 allows an organization to use a consistent backup and recovery process across multiple workloads such as File servers, SQL, Hyper-V, and SharePoint. DPM 2010 and other Exchange Roles When protecting Exchange Server 2010, administrators must consider how other Exchange Server roles such as the Hub Transport and Client Access Server should be
DPM2010_Whitepaper_How_to_protect_Exchange.docx