asked on
Distributed File System Is Stuck
I am running DFS in my environment and I have run up against a problem. I have four servers: WSCALFS, FARM1, FARM2, and FARM3.
WSCALFS is not working properly anymore: The DFS Replication service stopped replication on volume G:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
The DFS Replication service stopped replication on volume N:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
The DFS Replication service stopped replication on volume U:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
The biggest problem with this is that some people have been working off WSCALFS and some people have been working off the shared replication server.
I found an article about recovering from this problem, making the crashed server the primary server, but I am not sure that that is what I want to do. https://support.microsoft.com/en-us/help/961879/how-to-recover-from-a-dfsr-database-crash-on-designated-primary-member
Any advice?
WSCALFS is not working properly anymore: The DFS Replication service stopped replication on volume G:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
The DFS Replication service stopped replication on volume N:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
The DFS Replication service stopped replication on volume U:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
The biggest problem with this is that some people have been working off WSCALFS and some people have been working off the shared replication server.
I found an article about recovering from this problem, making the crashed server the primary server, but I am not sure that that is what I want to do. https://support.microsoft.com/en-us/help/961879/how-to-recover-from-a-dfsr-database-crash-on-designated-primary-member
Any advice?
Windows Server 2012
Last Comment
arnold