Question Locked

W2K3 Server with DFS updating large files.

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a problem with large editable files shared across several sites. With DFS in place, the files update and slow the system right down to a snails pace. One possible solution is to allow them to update at the end of the working day, but this negates the fault tolerance provided by using DFS. Another problem is multiple users making alterations to the files through the course of the day. Is there a way to maintain the fault tolerance and reduce the slowing of the whole network. Thank you for your time.

3 replies

by wnfaknd

Were you able to find a solution to this problem?

by leodorado

Have you tried DFS in Windows Server 2003 R2? DFS was redesigned so it doesn't use File Replication Service anymore. R2 has a new service called DFS Replication which improves the way files replicates between nodes. This service pre-stages files so when a file is modified, it only replicates the changes. It also uses file compression, consuming very little bandwidth.

The Distributed File System snap-in was also improved. Among other things, you can order the way referals are offered to users, so they only access one server (preventing users to alter the same file in different servers) and in the case the node fails, users access the second referal.

Windows Server 2003 R2 offers a lot of improvements for File and Print Servers, I suggest you to visit Microsoft's Web page.

Regards,

Leo_

This discussion is closed to new replies.