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?
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 3 Answers and 3 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.
The Most Valuable Expert award recognizes technology experts who passionately share their knowledge with the community, demonstrate the core values of this platform, and go the extra mile in all aspects of their contributions. This award is based off of nominations by EE users and experts. Multiple MVEs may be awarded each year.
The Distinguished Expert awards are presented to the top veteran and rookie experts to earn the most points in the top 50 topics.