DPM 2010 Protecting Exchange 2010 DAG in a Single Site (HA but no DR)

Why should you backup an Exchange 2010 DAG implementation with DPM? What should you be thinking about before you make a final decision? What's the way out of this conundrum? ….Well, it depends. First, let us make a couple of seminal assumptions: ·That you’ll have more than one copy of an Exchange DB in a […]

Why should you backup an Exchange 2010 DAG implementation with DPM? What should you be thinking about before you make a final decision? What's the way out of this conundrum? ….Well, it depends. First, let us make a couple of seminal assumptions: ·That you’ll have more than one copy of an Exchange DB in a DAG. OK, you're allowed a duh! · That you’ll be deploying Exchange 2010 DAG with cheap JBODs, which’ll undoubtedly save you a bundle. · If you’re going to use JBOD, then you really understand how to interpret MTBF and its relationship to uptime SLA. All Exchange Mailbox Servers in one site (HA but no DR) “If you want to deploy Exchange 2010 with JBOD, it is recommended that you should deploy with at least three copies. In addition to this, if you want to also use DAG copies for Point In Time (PIT) recovery, then you’ll need a server to host lagged copy of the DB. Lagged copies are a means to safeguard against store/logical corruption events (and possibly accidental mailbox deletions). If you’re going to distribute lagged copies among your primary severs, then you’ll need at least two lagged copies. If you’re going to use dedicated servers with lagged copies with JBOD, for better reliability you’re well advised to deploy enough servers to house two lagged copies; otherwise you could deploy dedicated lagged copy servers with RAID and thus only have one lagged copy per database[…]”

Full Article: DPM blog