I evaluated DPM several years ago and chose against it for reasons like this (and some others). I did not see it as a mature or very well supported product. I'm sure things have improved. Perhaps you have to find the right list? On Jul 28, 2014 4:07 PM, "Daniel Chenault" <[email protected]> wrote:
> 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] > To: [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]] *On Behalf Of *Daniel Chenault > *Sent:* Monday, July 28, 2014 3:55 PM > *To:* [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. >
