The new DPM 2010 (DPM v3), of course, has support for Exchange 2010 databases protected by a Database Availability Group (DAG) as can be seen from the below screenshot (which needs to have the Exchange logo updated BTW).
When backing up DAG protected databases, it’s recommend to perform the Eseutil integrity check for the log files only.
DPM 2010 can even perform backups of multiple copies of the same database.
Below the initial replica of each database is being created.
Here we can see informational alerts about the jobs currently running.
We have now created the first replica successfully and therefore also flushed the log files on each DB copy in the DAG.
Windows Server Backup 2008 SP2 or R2 together with the VSS plug-in included with Exchange 2010 can also backup DAG protected databases, but only via the active database copy. And since the VSS plug-in (like DPM 2010) doesn’t have any intelligence built in to detect which Exchange 2010 Mailbox server holds the active database copy, managing backups of DAG protected databases can quickly become cumbersome.
Recovering databases are also very similar to previous versions of DPM.
Recovering data from Exchange 2010 databases.
But we still need to recover the whole database holding the particular mailbox we want to recover.
Or you can recover at the database level.
Note the third option below. As we no longer have the concept of storage groups in Exchange 2010, we also don’t have recovery storage groups (RSGs). We now have so called recovery databases (RDBs) to which we can restore and mount databases. We can then merge content from mailboxes in the recovery database to the production database as needed.
You should of course not use this DPM 2010 beta version in production, but it’s good to have an alternative to WSB and the VSS plug-in for backing up your Exchange 2010 lab environments. As you can see below we can restore on the mailbox level.
MCM: Exchange 2007 | MVP: Exchange Architecture
MCITP: EMA + EA | MCSE: M + S | TechNet Influent