Discussion:
Does changing a bridgehead server cause a SYSVOL refresh?
(too old to reply)
Trust No One
2009-04-23 07:19:47 UTC
Permalink
Hi Folks,

Appreciate if someone could clarify whether a change of a bridgehead
server (for example a rebuild due to hardware change) will cause all
the replication partners affected to do a complete refresh (D2) of
their SYSVOL contents?

I know that the KCC will create new connections and that this involves
FRS vvjoins. What I'm not clear about is whether all the replication
partners affected will dump their current SYSVOL and replicate it
afresh over the new connection object. This would have a huge network
impact, so I'm after some clarity on whether this will be the case.

Could anyone clarify?


--
Peter <X-File Fan>
Florian Frommherz [MVP]
2009-04-23 09:33:11 UTC
Permalink
Howdie!
Post by Trust No One
I know that the KCC will create new connections and that this involves
FRS vvjoins. What I'm not clear about is whether all the replication
partners affected will dump their current SYSVOL and replicate it
afresh over the new connection object. This would have a huge network
impact, so I'm after some clarity on whether this will be the case.
No they don't. The new bridgehead server is elected and starts its work
right-away. There is no re-sync of the SYSVOL or any partition of the
database.

Cheers,
Florian
--
Microsoft MVP - Group Policy
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
Maillist (german): http://frickelsoft.net/cms/index.php?page=mailingliste
Trust No One
2009-04-23 10:59:20 UTC
Permalink
On Apr 23, 10:33 am, "Florian Frommherz [MVP]"
Post by Florian Frommherz [MVP]
Howdie!
Post by Trust No One
I know that the KCC will create new connections and that this involves
FRS vvjoins. What I'm not clear about is whether all the replication
partners affected will dump their current SYSVOL and replicate it
afresh over the new connection object. This would have a huge network
impact, so I'm after some clarity on whether this will be the case.
No they don't. The new bridgehead server is elected and starts its work
right-away. There is no re-sync of the SYSVOL or any partition of the
database.
Thanks for that Florian!

One less thing to worry about as I'll be rebuilding all our bridgehead
domain controller due to a hardware refresh.

--
Peter <X-Files Fan>
Paul Bergson [MVP-DS]
2009-04-23 12:18:43 UTC
Permalink
No there would be no reason for this to occur. Changes are tracked and
replication will only occur if an object within sysvol has changed.
--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.
Post by Trust No One
Hi Folks,
Appreciate if someone could clarify whether a change of a bridgehead
server (for example a rebuild due to hardware change) will cause all
the replication partners affected to do a complete refresh (D2) of
their SYSVOL contents?
I know that the KCC will create new connections and that this involves
FRS vvjoins. What I'm not clear about is whether all the replication
partners affected will dump their current SYSVOL and replicate it
afresh over the new connection object. This would have a huge network
impact, so I'm after some clarity on whether this will be the case.
Could anyone clarify?
--
Peter <X-File Fan>
Marcin
2009-04-23 21:09:00 UTC
Permalink
Peter,
this really depends on circumstances. At the very least, vvjoin tends to be
processor intensive - but in some cases it might actually trigger full
SYSVOL replication (in particular, you should be careful about using a
prestaged replica member - which seems to be the scenario you are referring
to). For more details, refer to the How the Vvjoin Process Works section of
http://technet.microsoft.com/en-us/library/cc758169.aspx

hth
Marcin
Post by Trust No One
Hi Folks,
Appreciate if someone could clarify whether a change of a bridgehead
server (for example a rebuild due to hardware change) will cause all
the replication partners affected to do a complete refresh (D2) of
their SYSVOL contents?
I know that the KCC will create new connections and that this involves
FRS vvjoins. What I'm not clear about is whether all the replication
partners affected will dump their current SYSVOL and replicate it
afresh over the new connection object. This would have a huge network
impact, so I'm after some clarity on whether this will be the case.
Could anyone clarify?
--
Peter <X-File Fan>
Meinolf Weber [MVP-DS]
2009-04-26 18:53:16 UTC
Permalink
Hello Trust,

No, it wan't do it with just changing the bridgehead server as described
from the others.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Post by Trust No One
Hi Folks,
Appreciate if someone could clarify whether a change of a bridgehead
server (for example a rebuild due to hardware change) will cause all
the replication partners affected to do a complete refresh (D2) of
their SYSVOL contents?
I know that the KCC will create new connections and that this involves
FRS vvjoins. What I'm not clear about is whether all the replication
partners affected will dump their current SYSVOL and replicate it
afresh over the new connection object. This would have a huge network
impact, so I'm after some clarity on whether this will be the case.
Could anyone clarify?
--
Peter <X-File Fan>
Loading...