DFS // What target will be used????

  • Thread starter Thread starter Marcus Wolf
  • Start date Start date
M

Marcus Wolf

Hi there,



I won't to set up a AD-integrated DFS which has lot's of links. Since the
DFS is used worldwide, each link shoud have at least four targets (servers).
How can I make sure that only one target is modified, and the modifications
is replicated onto the other targets?

Regards Marcus
 
Hi Mukul!

The other four target should only be used as "read-only" or fail-over or
maintenance on the "main target"

Also one scenario we are considering is deploying msi-packages worldwide.
That would mean that a group would create and modify them and store them on
target one. After that they should be replicated to the other targets.
Therefor we must insure somehow that the targets two-four are read-only for
the clients.


Thanks for your help,

Marcus



Mukul Gupta said:
Do you mean that clients (all clients??) should go to only one of 4 targets
for writing while they (all clients??) be able to read from all 4 targets?

Are all clients expected to write or is only some particular process/group
expected to write to link?

Please provide more information about your write/read scenario requirements.

--
Thanks
Mukul [MSFT]

PS: Please post DFS related queries in newsgroup
microsoft.public.win2000.file_system. Please use "DFS" in subject to make it
immediately noticeable.

Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights

Marcus Wolf said:
Hi there,



I won't to set up a AD-integrated DFS which has lot's of links. Since the
DFS is used worldwide, each link shoud have at least four targets (servers).
How can I make sure that only one target is modified, and the modifications
is replicated onto the other targets?

Regards Marcus
 
If I understand correctly, this is your scenario:

1. You need 4 targets for a link
2. 1st one (or one of them) is "maintainence target" where you will
write/change data
3. You want this data to replicate to other 3 targets
4. Client should go to only other 3 targets for "reading data"

This is quite common scenario...
For this, you can do the following...

\\domain\root\link --> \\srv1\maintainenceshare
--> \\srv2\readshare1
--> \\srv3\readshare2
--> \\srv4\readshare3


1. Create the link with 4 targets and enable replication on them, with
master as your 1st or "maintainence target"
2. Set "read-only" permissions of 2-4 targets for clients
(\\srv2\readshare1, \\srv3\readshare2, \\srv4\readshare3), so clients will
have only read-only permission on these targets.
2. Make 1st-target/maintainence-target offline in DFSGUI
(\\srv1\maintainenceshare). This won't affect replication from this target.
After this step, clients will get DFS referrals with only remaining 3
targets so they will go to only remaining 3 targets
3. Maintaince group/team should directly write data to 4th target
(\\srv1\maintainenceshare)

So this way, data will continue replicating from maintainence target to
other 3 visible targets to which clients have read-only access.

--
Thanks
Mukul [MSFT]

PS: Please post DFS related queries in newsgroup
microsoft.public.win2000.file_system. Please use "DFS" in subject to make it
immediately noticeable.

Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights

Marcus Wolf said:
Hi Mukul!

The other four target should only be used as "read-only" or fail-over or
maintenance on the "main target"

Also one scenario we are considering is deploying msi-packages worldwide.
That would mean that a group would create and modify them and store them on
target one. After that they should be replicated to the other targets.
Therefor we must insure somehow that the targets two-four are read-only for
the clients.


Thanks for your help,

Marcus



Mukul Gupta said:
Do you mean that clients (all clients??) should go to only one of 4 targets
for writing while they (all clients??) be able to read from all 4 targets?

Are all clients expected to write or is only some particular process/group
expected to write to link?

Please provide more information about your write/read scenario requirements.

--
Thanks
Mukul [MSFT]

PS: Please post DFS related queries in newsgroup
microsoft.public.win2000.file_system. Please use "DFS" in subject to
make
it
immediately noticeable.

Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights
 
Back
Top