|
Maybe I need to describe my environment a little more…we have 3 file servers that have a common file structure with one server holding a master directory structure that is copied to both itself (with xcopy) and to the other two servers with robocopy. To ensure that a file actually does get copied, via a daily scheduled job we need to stop the server service and kick off each of the current user connections (net session \\computer_name_here /delete) to make sure no one has a file open before the xcopy/robocopy process starts. Note each of these users will only have a particular file(s) open for read access.
With the latest DFS process using dynamic file replication (yes, I know we can schedule the replication times), I wonder what would happen when a file is updated and a user still has it open. Hope this explanation makes things a little clearer.
Mike Thommes
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ion Gott
The client will continue to have the file open but depends on what action they take next...if they close the file..nothing.
If they save the file, the last write is going to win and possibly replace the changes that were made on the file saved previously that the user may not be aware of.
The work around for this issue really depends on the structure of your DFS environment, I tend to use DFS-R to just replicate data and disable referrals to that backup server so that doesn't happened.
Depends on exactly how your using it I guess...
From:
[EMAIL PROTECTED] on behalf of Thommes, Michael M. Can
someone tell me what happens with DFS/replication when a file is |
Title: [ActiveDir] 2003 DFS/open files
- RE: [ActiveDir] 2003 DFS/open files Thommes, Michael M.
- Re: [ActiveDir] 2003 DFS/open files Steven Comeau
- RE: [ActiveDir] 2003 DFS/open files Bernard, Aric
- Re: [ActiveDir] 2003 DFS/open files Steven Comeau
