DFS - practical uses ?

Hi, I have a site where they want to use DFS shares so that users at both
sites over a slow WAN connection can access files quickly.

Question.

Is this best suited to scenarios where one user might commute between both
sites and want his/her files readily available for quick access ?

Or how about a number of users all frequently wanting to share and open the
same documents from both sites.
Ie several users may all want to open the same documents, would this be a
good idea ?
What happens if several users open the same document and make changes to it
? whose change is kept and how is this managed ?
How does the file locking work ?

Jim.

On Thu, 12 Nov 2009 13:05:13 -0000, "Jim" <> wrote:

>Hi, I have a site where they want to use DFS shares so that users at both
>sites over a slow WAN connection can access files quickly.
>

Two sites presumably :-)


>Question.
>
>Is this best suited to scenarios where one user might commute between both
>sites and want his/her files readily available for quick access ?

For home folder etc. where only one user access the set of file this works well.

>
>Or how about a number of users all frequently wanting to share and open the
>same documents from both sites.
>Ie several users may all want to open the same documents, would this be a
>good idea ?
>What happens if several users open the same document and make changes to it
>? whose change is kept and how is this managed ?
Last write wins. DFS detects this a move the other changed copied to
"Conflicted". An admin needs to resolve this issue.

>How does the file locking work ?
There is none (except the normal single copy stuff) so if two users open the
same copy there is the usual "in use" warning but if they open copies on two
replicas they get no warning.


>
>Jim.
>
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

Yeah, two sites,

Users at both sites are likely to open copies of the same file at either
site, I can see this casuing issues.

So you're saying that the last write/save wins and the other copy goes into
a 'conflict' area ?

Doesn't sound well suited to this type of use does it.

Other than that you seem to indicate that it is better suited to communting
users wanting to access their own home folders from different sites quickly
with the replication keeping up to date copies of the same files at both
ends.

Jim.



"DaveMills" <> wrote in message
news:...
> On Thu, 12 Nov 2009 13:05:13 -0000, "Jim" <> wrote:
>
>>Hi, I have a site where they want to use DFS shares so that users at both
>>sites over a slow WAN connection can access files quickly.
>>
>
> Two sites presumably :-)
>
>
>>Question.
>>
>>Is this best suited to scenarios where one user might commute between both
>>sites and want his/her files readily available for quick access ?
>
> For home folder etc. where only one user access the set of file this works
> well.
>
>>
>>Or how about a number of users all frequently wanting to share and open
>>the
>>same documents from both sites.
>>Ie several users may all want to open the same documents, would this be a
>>good idea ?
>>What happens if several users open the same document and make changes to
>>it
>>? whose change is kept and how is this managed ?
> Last write wins. DFS detects this a move the other changed copied to
> "Conflicted". An admin needs to resolve this issue.
>
>>How does the file locking work ?
> There is none (except the normal single copy stuff) so if two users open
> the
> same copy there is the usual "in use" warning but if they open copies on
> two
> replicas they get no warning.
>
>
>>
>>Jim.
>>
> --
> Dave Mills
> There are 10 types of people, those that understand binary and those that
> don't.

On Mon, 16 Nov 2009 09:36:21 -0000, "Jim" <> wrote:

>Yeah, two sites,
>
>Users at both sites are likely to open copies of the same file at either
>site, I can see this casuing issues.
>
>So you're saying that the last write/save wins and the other copy goes into
>a 'conflict' area ?
>
>Doesn't sound well suited to this type of use does it.
>
>Other than that you seem to indicate that it is better suited to communting
>users wanting to access their own home folders from different sites quickly
>with the replication keeping up to date copies of the same files at both
>ends.
It is also useful for read only folders where updates are made by just a few
people centrally but local copies are needed by all.

The effect of not having file locking will depend upon how your company works
but you do need to be careful.
>
>Jim.
>
>
>
>"DaveMills" <> wrote in message
>news:.. .
>> On Thu, 12 Nov 2009 13:05:13 -0000, "Jim" <> wrote:
>>
>>>Hi, I have a site where they want to use DFS shares so that users at both
>>>sites over a slow WAN connection can access files quickly.
>>>
>>
>> Two sites presumably :-)
>>
>>
>>>Question.
>>>
>>>Is this best suited to scenarios where one user might commute between both
>>>sites and want his/her files readily available for quick access ?
>>
>> For home folder etc. where only one user access the set of file this works
>> well.
>>
>>>
>>>Or how about a number of users all frequently wanting to share and open
>>>the
>>>same documents from both sites.
>>>Ie several users may all want to open the same documents, would this be a
>>>good idea ?
>>>What happens if several users open the same document and make changes to
>>>it
>>>? whose change is kept and how is this managed ?
>> Last write wins. DFS detects this a move the other changed copied to
>> "Conflicted". An admin needs to resolve this issue.
>>
>>>How does the file locking work ?
>> There is none (except the normal single copy stuff) so if two users open
>> the
>> same copy there is the usual "in use" warning but if they open copies on
>> two
>> replicas they get no warning.
>>
>>
>>>
>>>Jim.
>>>
>> --
>> Dave Mills
>> There are 10 types of people, those that understand binary and those that
>> don't.
>
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.