There is almost always a reason. :) Some of them take longer to figure out than others. You must consolidate information from event logs, the DPM logs, and the crimson log.
Also, DPM separates some capabilities that you may consider part of the "backup" responsibility to the OS (e.g., dedupe - that is an OS responsibility). I've been very happy with DPM, but getting it to be stable in a complex environment can take some work. You can figure it out by yourself, with a consultant, or with MSFT support. To Dan's original question... there are two different Exchange VSS writers - one for the replica and one for the primary. They both have to be working properly. From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Chenault Sent: Monday, July 28, 2014 4:06 PM To: [email protected] Subject: RE: [Exchange] DAG & DPM Oh yeah, I REALLY dislike how DPM is not very helpful when it runs into problems. "There is a problem with VSS on the source machine." ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: RE: [Exchange] DAG & DPM Date: Mon, 28 Jul 2014 20:03:13 +0000 I would like to follow this convo as well. I continue to get DPM errors but no real reason that I can figure? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Chenault Sent: Monday, July 28, 2014 3:55 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] DAG & DPM I inherited this setup and am just trying to make heads or tails of the continuing problems (mostly "replica out of sync"). How does DPM handle the log files in a DAG? Does it only backup the active DB and... then what? I've read two books thus far on DPM and Exchange and neither went into the actual workings under the hood; mostly screen shots of how to set this or that up. Had a situation where a backup kept failing for no good reason I could see. Had to failover the DB to it's partner (unrelated) and all of a sudden the logs cleared. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email.
