I have 2 DC's running Windows Server 2008 SP2. They are protected by Data Protection Manager 2007 SP1 with a system state backup. I recently migrated to DFSR for my SYSVOL directory and ever since I get Event ID 5014 "The DFS Replication service is stopping communication with partner <<servername>> for replication group Domain System Volume due to an error. The service will retry the connection periodically. " Error: 9033 (The request was cancelled by a shutdown) Connection ID: 62519AD7-185E-45D7-A8F3-984AD0F38B55 Replication Group ID: A1C83FC5-A042-4F76-A124-6B10E84F6247 This error occurs and the same time each day at the precise time that DPM is doing the system state backup. Is there a good DFSR forum or DPM forum to have this question addressed? I found a couple newsgroup articles which seem to point to the same problem, only for DPM 2010 beta http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.dataprotectionmanager&tid=adbae81c-b3f4-4b38-9628-97207b14fa8c&cat=en_US_c18d9b67-8a4f-493f-99fa-246042fd5824&lang=en&cr=US&sloc=en-us&m=1&p=1 This seems like a potential fix, but not sure if it applies to DPM 2007 SP1 http://65.55.21.250/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.dataprotectionmanager&tid=b41e4c82-d524-4dfa-9e37-195696742ce9&cat=en_US_c18d9b67-8a4f-493f-99fa-246042fd5824&lang=en&cr=US&sloc=&p=1

I should add that replication goes on it's merry way once system state backup is complete...just annoying that replication crashes each day because of backup

I just put in a DFSR/DPM combo in a test environment and have noticed the same issues w/ DPM2k10beta + R2 DFSR. DFSR service stops citing an IO conflict. It doesn't appear to correct itself for me unless I disable the DPM agent. What and royal pain!

Hi customer, According to my research, I have confirmed that the issue can be reproducing on my side on Windows Server 2008 when DPM is interoperating with DFSR. We are sorry for causing the incontinence to you. Our product team has been aware of this issue and it will be fixed in the next version of Windows. Thanks for the understandings.This posting is provided "AS IS" with no warranties, and confers no rights.

Not sure if I read that correctly. Are you saying the next version of windows? Do you mean whatever is after server 2k8R2? So there is no way to address the conflict somehow in the release of DPM2k10? If I'll have to wait until the next OS to fix this backup issue I guess its time to start looking for an alternative to DPM :-/Hopefully I've missread your post, but if not, thanks for the headsup.