hub/spoke

windows 2003 r2

After a hub/spoke is done, all members become multi-replication or all equal
parnters.

To maintain a hub and NOT to receive updates from branch (hub only pushes
files to branch), i need to disable connection from branch partners ?

> To maintain a hub and NOT to receive updates from branch (hub only pushes
> files to branch), i need to disable connection from branch partners ?


In the early R2 days they touted one way replication like you are
suggesting. Then they backed off on one way replication because it would
"fix" itself and become two way again. Last I heard was not to use one way
replication. (Win 2k8 may be different)

If possible on the branch (spokes) I would set permissions so they can not
add/change files in replicated folder.

hth
DDS


"IT Staff" <> wrote in message
news:...
> windows 2003 r2
>
> After a hub/spoke is done, all members become multi-replication or all
> equal parnters.
>
> To maintain a hub and NOT to receive updates from branch (hub only pushes
> files to branch), i need to disable connection from branch partners ?
>
>
>
>
>

i raise this question because i read a very old article that states that if
u use hub/spoke, remember to disable one of the direction flow. Otherwise it
become a mesh network atuomatically (both can send to each other after the
initial hub/spoke replication completes)

I don't know whether this is change in win2k8, but i will find from MS then.





"Danny Sanders" <> wrote in message
news:%...
>> To maintain a hub and NOT to receive updates from branch (hub only pushes
>> files to branch), i need to disable connection from branch partners ?
>
>
> In the early R2 days they touted one way replication like you are
> suggesting. Then they backed off on one way replication because it would
> "fix" itself and become two way again. Last I heard was not to use one way
> replication. (Win 2k8 may be different)
>
> If possible on the branch (spokes) I would set permissions so they can not
> add/change files in replicated folder.
>
> hth
> DDS
>
>
> "IT Staff" <> wrote in message
> news:...
>> windows 2003 r2
>>
>> After a hub/spoke is done, all members become multi-replication or all
>> equal parnters.
>>
>> To maintain a hub and NOT to receive updates from branch (hub only pushes
>> files to branch), i need to disable connection from branch partners ?
>>
>>
>>
>>
>>
>
>

can i cheat the systems by doing the following ?

a) make a R2 a hub, make a non-r2 a spoke.
b) non-r2 machine cannot replicate, so it is always a receiver from hub ?







"Danny Sanders" <> wrote in message
news:%...
>> To maintain a hub and NOT to receive updates from branch (hub only pushes
>> files to branch), i need to disable connection from branch partners ?
>
>
> In the early R2 days they touted one way replication like you are
> suggesting. Then they backed off on one way replication because it would
> "fix" itself and become two way again. Last I heard was not to use one way
> replication. (Win 2k8 may be different)
>
> If possible on the branch (spokes) I would set permissions so they can not
> add/change files in replicated folder.
>
> hth
> DDS
>
>
> "IT Staff" <> wrote in message
> news:...
>> windows 2003 r2
>>
>> After a hub/spoke is done, all members become multi-replication or all
>> equal parnters.
>>
>> To maintain a hub and NOT to receive updates from branch (hub only pushes
>> files to branch), i need to disable connection from branch partners ?
>>
>>
>>
>>
>>
>
>

No. When setting up the replication group from the hub, using the DFSR
management console, when you select the remote replication partner it will
want the partner to at the R2 level also.

hth
DDS

"IT Staff" <> wrote in message
news:%...
> can i cheat the systems by doing the following ?
>
> a) make a R2 a hub, make a non-r2 a spoke.
> b) non-r2 machine cannot replicate, so it is always a receiver from hub ?
>
>
>
>
>
>
>
> "Danny Sanders" <> wrote in message
> news:%...
>>> To maintain a hub and NOT to receive updates from branch (hub only
>>> pushes files to branch), i need to disable connection from branch
>>> partners ?
>>
>>
>> In the early R2 days they touted one way replication like you are
>> suggesting. Then they backed off on one way replication because it would
>> "fix" itself and become two way again. Last I heard was not to use one
>> way replication. (Win 2k8 may be different)
>>
>> If possible on the branch (spokes) I would set permissions so they can
>> not add/change files in replicated folder.
>>
>> hth
>> DDS
>>
>>
>> "IT Staff" <> wrote in message
>> news:...
>>> windows 2003 r2
>>>
>>> After a hub/spoke is done, all members become multi-replication or all
>>> equal parnters.
>>>
>>> To maintain a hub and NOT to receive updates from branch (hub only
>>> pushes files to branch), i need to disable connection from branch
>>> partners ?
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>

In message <#> "IT Staff"
<> was claimed to have wrote:

>can i cheat the systems by doing the following ?
>
>a) make a R2 a hub, make a non-r2 a spoke.
>b) non-r2 machine cannot replicate, so it is always a receiver from hub ?

No. Replication is what handles the data moving both directions, a
non-R2 machine can neither send nor receive.