I do not have an issue, just need to clarify a few things and see if in my scenario, are there any after effects.
We are using DPM 2010 with all service patches on a 2008r2 physical box
We have Exchange 2010 in a DAG configuration. Two exchnage (exchange1 and exchange2) boxes control access to he mailbox database. these are 2008r2 physical boxes with Exchange 2010 sp2 rollup 6. ( we have not made the move to sp3 yet.)
In dpm, we have exchange in a PG. using the eseutil locally on dpm. and have it set Run for log files only. The Database copy for a full backup is set against our exchange1 box for the mailbox database and public folders database. Also, there is a Synchronization frequency set for 15 minutes.
What we are seeing is when the mailbox database is mounted on exchange1; all work well. No uncommn event are recorded.
However, when the mailbox database is mounted on exchange2, there are many many more events written. it looks like the Information Store for the mailbox database is stoppped, there is a VSS writter freeze against the database. I see that an incremental backup has started, has stopped, then the database is thawed, mounted etc... These are all successful messages. There are no issues or errors.
I am just interested to know why this happens, if there is a scenario or type of Protection group configuration that I can make to prevent this, or if i can expect and sort of impact on dpm, the exchange servers, or all the way down to the user experience.
thanks
Ian
Ian