Discussion:
DFS Replication
(too old to reply)
Claudio
2006-07-21 14:51:02 UTC
Permalink
Hello, i have two Windows Server 2003 Standard R2, and two shared folders,
one on each server, i have configured a DFS Spacename on one of them, and
independent root, and a replication root have been created.
Replication works fine, but when i open a file on a folder on server1 , and
someone else tries to open the same file on server2 ,a Word file, for
example, Word didn´t show that the file is opened.
I have erased the filter parameters, that don´t allow files (~*,..), so
these files are replicated and i can see them on the server2, but still, Word
doesn´t notice that the file is opened on the other directory.
Any ideas? what can i do?
Jill Zoeller [MSFT]
2006-07-21 15:23:46 UTC
Permalink
Claudio, this behavior is by design. DFS Replication does not provide any
sort of locking mechanism to prevent a file from being opened on a server
when the file is already open elsewhere. This is one of the reasons why we
recommend using DFSR in scenarios where these conflicts are unlikely to
occur, can be minimized, or can be tolerated. For example, we recommend DFSR
for data collection and data publishing, and we consider the "loose
collaboration" scenario to be one in which occasional conflicts can be
tolerated.

Shared folder permissions can be used to prevent changes from occurring on
one of the servers.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
Post by Claudio
Hello, i have two Windows Server 2003 Standard R2, and two shared folders,
one on each server, i have configured a DFS Spacename on one of them, and
independent root, and a replication root have been created.
Replication works fine, but when i open a file on a folder on server1 , and
someone else tries to open the same file on server2 ,a Word file, for
example, Word didnŽt show that the file is opened.
I have erased the filter parameters, that donŽt allow files (~*,..), so
these files are replicated and i can see them on the server2, but still, Word
doesnŽt notice that the file is opened on the other directory.
Any ideas? what can i do?
Claudio
2006-07-24 10:19:02 UTC
Permalink
Hi, Jill
But, is it any way to activate or configure somehow that when you open a
file on one side the other knows this?
When i tried with FRS, it really works that´s why i configured two R2
servers, because of the new replication system, that is faster than the FRS.
Sorry i bother you with this, is really important that no one overwrites a
file opened.
Thanks for your help.
Post by Jill Zoeller [MSFT]
Claudio, this behavior is by design. DFS Replication does not provide any
sort of locking mechanism to prevent a file from being opened on a server
when the file is already open elsewhere. This is one of the reasons why we
recommend using DFSR in scenarios where these conflicts are unlikely to
occur, can be minimized, or can be tolerated. For example, we recommend DFSR
for data collection and data publishing, and we consider the "loose
collaboration" scenario to be one in which occasional conflicts can be
tolerated.
Shared folder permissions can be used to prevent changes from occurring on
one of the servers.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
Post by Claudio
Hello, i have two Windows Server 2003 Standard R2, and two shared folders,
one on each server, i have configured a DFS Spacename on one of them, and
independent root, and a replication root have been created.
Replication works fine, but when i open a file on a folder on server1 , and
someone else tries to open the same file on server2 ,a Word file, for
example, Word didn´t show that the file is opened.
I have erased the filter parameters, that don´t allow files (~*,..), so
these files are replicated and i can see them on the server2, but still, Word
doesn´t notice that the file is opened on the other directory.
Any ideas? what can i do?
Jill Zoeller [MSFT]
2006-07-24 15:22:32 UTC
Permalink
Hi Claudio,

Neither FRS nor DFS Replication offers distributed file locking. Both use a
"last writer wins" algorithm for determing which version of the file to
keep. With FRS, the changes will be overwritten completely by the winning
file, and there is no way to retrieve the losing version. With DFS
Replication, the "losing" file is moved to a special subfolder where an
admin can retrieve it (assuming the folder hasn't been purged).

If you want to avoid having conflicts, you have to make sure that only one
of the servers is writeable, whereas the other servers are read-only. This
can be accomplished using shared folder permissions.

Also, there are 3rd-party solutions out there that might work for you.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
Post by Claudio
Hi, Jill
But, is it any way to activate or configure somehow that when you open a
file on one side the other knows this?
When i tried with FRS, it really works thatŽs why i configured two R2
servers, because of the new replication system, that is faster than the FRS.
Sorry i bother you with this, is really important that no one overwrites a
file opened.
Thanks for your help.
Post by Jill Zoeller [MSFT]
Claudio, this behavior is by design. DFS Replication does not provide any
sort of locking mechanism to prevent a file from being opened on a server
when the file is already open elsewhere. This is one of the reasons why we
recommend using DFSR in scenarios where these conflicts are unlikely to
occur, can be minimized, or can be tolerated. For example, we recommend DFSR
for data collection and data publishing, and we consider the "loose
collaboration" scenario to be one in which occasional conflicts can be
tolerated.
Shared folder permissions can be used to prevent changes from occurring on
one of the servers.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
Post by Claudio
Hello, i have two Windows Server 2003 Standard R2, and two shared folders,
one on each server, i have configured a DFS Spacename on one of them, and
independent root, and a replication root have been created.
Replication works fine, but when i open a file on a folder on server1 , and
someone else tries to open the same file on server2 ,a Word file, for
example, Word didnŽt show that the file is opened.
I have erased the filter parameters, that donŽt allow files (~*,..), so
these files are replicated and i can see them on the server2, but
still,
Word
doesnŽt notice that the file is opened on the other directory.
Any ideas? what can i do?
Claudio
2006-07-24 17:49:01 UTC
Permalink
Thanks, for your help, Jill
I only wanted to ask you for some name for the 3rd-party software that you
named.
That´s all, and thanks
Post by Jill Zoeller [MSFT]
Hi Claudio,
Neither FRS nor DFS Replication offers distributed file locking. Both use a
"last writer wins" algorithm for determing which version of the file to
keep. With FRS, the changes will be overwritten completely by the winning
file, and there is no way to retrieve the losing version. With DFS
Replication, the "losing" file is moved to a special subfolder where an
admin can retrieve it (assuming the folder hasn't been purged).
If you want to avoid having conflicts, you have to make sure that only one
of the servers is writeable, whereas the other servers are read-only. This
can be accomplished using shared folder permissions.
Also, there are 3rd-party solutions out there that might work for you.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
Post by Claudio
Hi, Jill
But, is it any way to activate or configure somehow that when you open a
file on one side the other knows this?
When i tried with FRS, it really works that´s why i configured two R2
servers, because of the new replication system, that is faster than the FRS.
Sorry i bother you with this, is really important that no one overwrites a
file opened.
Thanks for your help.
Post by Jill Zoeller [MSFT]
Claudio, this behavior is by design. DFS Replication does not provide any
sort of locking mechanism to prevent a file from being opened on a server
when the file is already open elsewhere. This is one of the reasons why we
recommend using DFSR in scenarios where these conflicts are unlikely to
occur, can be minimized, or can be tolerated. For example, we recommend DFSR
for data collection and data publishing, and we consider the "loose
collaboration" scenario to be one in which occasional conflicts can be
tolerated.
Shared folder permissions can be used to prevent changes from occurring on
one of the servers.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
Post by Claudio
Hello, i have two Windows Server 2003 Standard R2, and two shared folders,
one on each server, i have configured a DFS Spacename on one of them, and
independent root, and a replication root have been created.
Replication works fine, but when i open a file on a folder on server1 , and
someone else tries to open the same file on server2 ,a Word file, for
example, Word didn´t show that the file is opened.
I have erased the filter parameters, that don´t allow files (~*,..), so
these files are replicated and i can see them on the server2, but
still,
Word
doesn´t notice that the file is opened on the other directory.
Any ideas? what can i do?
Jill Zoeller [MSFT]
2006-07-24 18:00:41 UTC
Permalink
A good place to start is searching the web for WAFS solutions.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
Post by Claudio
Thanks, for your help, Jill
I only wanted to ask you for some name for the 3rd-party software that you
named.
ThatŽs all, and thanks
Post by Jill Zoeller [MSFT]
Hi Claudio,
Neither FRS nor DFS Replication offers distributed file locking. Both use a
"last writer wins" algorithm for determing which version of the file to
keep. With FRS, the changes will be overwritten completely by the winning
file, and there is no way to retrieve the losing version. With DFS
Replication, the "losing" file is moved to a special subfolder where an
admin can retrieve it (assuming the folder hasn't been purged).
If you want to avoid having conflicts, you have to make sure that only one
of the servers is writeable, whereas the other servers are read-only. This
can be accomplished using shared folder permissions.
Also, there are 3rd-party solutions out there that might work for you.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
Post by Claudio
Hi, Jill
But, is it any way to activate or configure somehow that when you open a
file on one side the other knows this?
When i tried with FRS, it really works thatŽs why i configured two R2
servers, because of the new replication system, that is faster than the FRS.
Sorry i bother you with this, is really important that no one overwrites a
file opened.
Thanks for your help.
Post by Jill Zoeller [MSFT]
Claudio, this behavior is by design. DFS Replication does not provide any
sort of locking mechanism to prevent a file from being opened on a server
when the file is already open elsewhere. This is one of the reasons
why
we
recommend using DFSR in scenarios where these conflicts are unlikely to
occur, can be minimized, or can be tolerated. For example, we
recommend
DFSR
for data collection and data publishing, and we consider the "loose
collaboration" scenario to be one in which occasional conflicts can be
tolerated.
Shared folder permissions can be used to prevent changes from
occurring
on
one of the servers.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
Post by Claudio
Hello, i have two Windows Server 2003 Standard R2, and two shared folders,
one on each server, i have configured a DFS Spacename on one of
them,
and
independent root, and a replication root have been created.
Replication works fine, but when i open a file on a folder on
server1 ,
and
someone else tries to open the same file on server2 ,a Word file, for
example, Word didnŽt show that the file is opened.
I have erased the filter parameters, that donŽt allow files (~*,..), so
these files are replicated and i can see them on the server2, but
still,
Word
doesnŽt notice that the file is opened on the other directory.
Any ideas? what can i do?
Continue reading on narkive:
Loading...