Forum Discussion
Ashish Gupta
Apr 07, 2017Copper Contributor
DFSR delete the file before replication
Hi, In our environment, we have two sites and both sites have two files servers. Like, Site 1 - ServerS101, ServerS102 Site 2- ServerS201, ServerS202 With this, there are three replication ...
- May 03, 2017
RDC is not involved here. The behavior you are describing is an interop problem between application behaviors in Office and with DFSR. Office operates differently than almost any user app on Earth in how it constantly locks, swaps, replaces files.
Did recreating file servers (I don;t know what this means) solve the issue? You need to reopen this case, MS Support should not have closed it, they should have escalated it.
NedPyle
Apr 26, 2017Former Employee
Hi. Did you apply this hotfix already? https://support.microsoft.com/en-us/help/3150126/replicated-files-are-deleted-on-all-the-other-dfsr-nodes-in-windows-server-2012-r2
Ashish Gupta
May 02, 2017Copper Contributor
Yes, it is already installed but still has the same problem. Btw, this update has been superseded by its July update. Still, the issue is not fixed.
- NedPyleMay 02, 2017Former Employee
Then it's not an issue I'm familiar with, and I recommend you open a case with MS Support. It could be a new bug.
- Ashish GuptaMay 03, 2017Copper Contributor
NedPyle A case was opened with MS and I worked with them for at least 6-7 days but it was not solved. They asked me to create all file servers again.
As far as I think, RDC is not working properly. Because files are replicating, but they get removed before replicating again. As per RDC, it should only replicate the changes to the file. If you have anything by which I can check the functionality of RDC and recommendations to check for RDC proper functionality. Please share it with me.
- NedPyleMay 03, 2017Former Employee
RDC is not involved here. The behavior you are describing is an interop problem between application behaviors in Office and with DFSR. Office operates differently than almost any user app on Earth in how it constantly locks, swaps, replaces files.
Did recreating file servers (I don;t know what this means) solve the issue? You need to reopen this case, MS Support should not have closed it, they should have escalated it.