Hey...ok so i have dfs running in 2008 domain...one namespace and 3 target servers...
Servers called A-B-C...Users use Server A,when that goes down they go to B and when that goes down they go to C...So as a test i shutdown Server A....Complaints of users....

1) when they switch over to Server B...some files where lost or outdated...i am assuming some files didnt get replicated from A to B fast enough...or at all....
2) connection times where real slow...so connecting to the namespace was very slow...like 1-2 minutes...

does anyone have any clue as to why this would happen and how to fix??
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Sounds like expected behavior to me. DFS is designed to provide a server-agnostic view of the file system through namespaces and solve some remote office pain points with replication. What you describe is more of a disaster recovery scenario, which was not the intended use for DFS. The feature set isn't really designed or meant for rapid failover. Windows has a completely unrelated feature set for those scenarios, and to really solve what you want, you'd be better served setting up a file server cluster.
SandeshdubeySenior Server EngineerCommented:
You need to first verfify the health of DFS by runing  Diagnostic Report for DFS Replication
http://technet.microsoft.com/en-us/library/cc754227.aspx and check this parameters as well listed in the link:http://networkadminkb.com/KB/a279/dfs-r-health-check.aspx

Checked the DFS event log for any errors and warming and post the same.

For slow replication see this:
Top 10 Common Causes of Slow Replication with DFSR:http://blogs.technet.com/b/askds/archive/2007/10/05/top-10-common-causes-of-slow-replication-with-dfsr.aspx

Configure Staging if not configured correctly.http://social.technet.microsoft.com/Forums/windowsserver/en-US/4c7d8022-9f26-4e54-9c5a-c101ecc68e78/dfs-replication-slow-in-one-direction-opposite-works-fine

Hope this helps

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.