Our friends over in the Data Protection Manager product group recently posted this article on how you can protect your Exchange 2010 high availability architecture using the next version of Data Pr...
Updated Jul 01, 2019
Version 2.0
Blog Post
1 MIN READ
Protecting Exchange 2010 DAG (Single Site) Using Data Protection Manager 2010
Hi Constantino,
Typically you need a backup to mitigate the following concerns:
1. Hardware/Software/Datacenter failures
2. Accidental/Malicious deletion of items
3. Logical corruption events / deleted mailboxes
Exchange 2010 offers the following features to help address those concerns:
1. Mailbox Resiliency (i.e. multiple database copies) helps mitigate Hardware/Software/Datacenter failures.
2. Single Item Recovery mitigates the need to restore backups to recover deleted items.
3. Point-in-time backups (like a lagged copy) can be used to mitigate the need to maintain backups for Logical corruption events / deleted mailbox recovery.
As for whether you need to have a solution to prevent logical corruption is something your business will need to decide as part of the risk mitigation planning process. The things to keep in mind with trying to recover from a logical corruption:
- You don't know a logical corruption has occurred until you are notified by the user(s).
- You don't know when the logical corruption occurred (reliant upon end user testimony as to when they discovered the data corruption).
- You need to have a point-in-time backup that goes back to that time frame.
- You need to make a decision as to how you will handle the recovery. Will you erase all new data to recover the data that was corrupted?
The answers to those questions will help drive whether you need to maintain a point-in-time backup for this scenario. If you decide you do need a point-in-time backup, then you need to decide what technology will you use. Will you use a lagged copy (replay lag max of 14 days) or a VSS backup solution like DPM. You do not need both.
Ross
Typically you need a backup to mitigate the following concerns:
1. Hardware/Software/Datacenter failures
2. Accidental/Malicious deletion of items
3. Logical corruption events / deleted mailboxes
Exchange 2010 offers the following features to help address those concerns:
1. Mailbox Resiliency (i.e. multiple database copies) helps mitigate Hardware/Software/Datacenter failures.
2. Single Item Recovery mitigates the need to restore backups to recover deleted items.
3. Point-in-time backups (like a lagged copy) can be used to mitigate the need to maintain backups for Logical corruption events / deleted mailbox recovery.
As for whether you need to have a solution to prevent logical corruption is something your business will need to decide as part of the risk mitigation planning process. The things to keep in mind with trying to recover from a logical corruption:
- You don't know a logical corruption has occurred until you are notified by the user(s).
- You don't know when the logical corruption occurred (reliant upon end user testimony as to when they discovered the data corruption).
- You need to have a point-in-time backup that goes back to that time frame.
- You need to make a decision as to how you will handle the recovery. Will you erase all new data to recover the data that was corrupted?
The answers to those questions will help drive whether you need to maintain a point-in-time backup for this scenario. If you decide you do need a point-in-time backup, then you need to decide what technology will you use. Will you use a lagged copy (replay lag max of 14 days) or a VSS backup solution like DPM. You do not need both.
Ross