Overcome file server latency between hub and branch offices
Posted on 2009-04-03
What options are available for the following situation?
" 1 hub office and several branch offices.
" 1 central file server at the hub office with several volumes, including a shared drive.
" 1 server located on site at each branch office.
" Issue with latency since the branch offices are so distant from the hub office.
Due to the latency issues we want to make one of the folders from the Hub file server available on the branch offices local file server (These folders are on the central file servers shared drive. We have tested DFS replication and that seemed to work well for the data replication from the central file server to the branch office file server).
However, we want the users to be able to use their existing mapped shared drive on the hub file server and when they get down to the replicated folder have them directed to their local server (the server at the branch office). If a user from the hub site does the same thing we want them to remain on the Hub file server and not be redirected to the branch office server which would defeat the purpose and create latency for the users at the hub office.