RE: Site Replication?

Yes - I've been looking at this with repadmin and now it all makes sense.

Thanks once again for your help!

--

Regards,
Matt MC




"Glenn L" wrote:

Inrasite replication is a notification based system. However, if no changes
occur for the time configured on the NTDS site settings object, then we will
attempt replication with our intrasite partners even though no changes have
occurred. In other words if no changes, we still try once per hour with our
intrasite peers.
The product does not want to assume no changes have occurred just because it
has not been notified, so it periodically trys to replicate once per hour by
default.

Ever notice repadmin /showreps and see that your schema partition has
replicated from other intrasite partners within the last hour? How often
does your schema change? Probably not more frequently than 1once per hour.

"Matt MC" wrote:

Hi Glenn,

Thanks for your reply! Much appreciated!

I now understand how it’s all working but still have one question.

If you select a site, go to NTDS Site Settings > click on View Schedule,
what is this / when is this schedule used?

If "Once per Hour" or "Four Times per Hour" is selected here, is this the
default schedule the KCC uses when creating its automatic connections?




--
Regards,
Matt MC




"Glenn L" wrote:

Based on what you configured, the branch office DC will attempt to inbound
replicate changes from the 2 DCs in the data center once every 15 minutes.

If that is what you wanted, then you are done.

AD repl engine uses the configuration on the connection object for its repl
behavior.

You did not have to create manual connections. the KCC in the branch office
would have automatically built a single connection from a random DC in the
datacenter based on your site link between the 2 sites. The resulting
connection would replicate only once every 180 minutes based on the site link
interval. automatic connection objects inherit the site link schedule and
interval settings.

Cheers

"Matt MC" wrote:

Hi Guys,

Its been so long since I studied this stuff and its not something I've
worked with much so a bit confused.


12 sites all connected to one DataCentre

SiteLinks created between each site and the DataCentre with Default
Replication of 180 minutes and Replication Availability set to always (24/7)

If I go to a Branch Office Site > NTDS Site Settings > View Schedule - its
set to "Once per Hour"

On the DC in the Branch Office I've created manual connections to pull
replication from the 2 DC's in the DataCentre.
The schedule for each of these connections is set to "Four Times per Hour"


How will my replicaiton take place?

Eg: If a change is made / new user created at one Branch Office, how long
will it take to replicate this to the DataCentre / another Branch Office.

All servers running Server 2003 SP1

TechNet doesn't talk about the Schedule settings on the site or Server
Connection, only the SiteLinks
http://technet2.microsoft.com/WindowsServer/en/Library/c283b699-6124-4c3a-87ef-865443d7ea4b1033.mspx?mfr=true

Was I wrong to manually create connections between the Branch Office DC and
the 2 DC's in the DataCentre?

Please let me know if you need anymore info.


--

Regards,
Matt MC


.

Relevant Pages

  • RE: Site Replication?
    ... Inrasite replication is a notification based system. ... If you select a site, go to NTDS Site Settings> click on View Schedule, ... You did not have to create manual connections. ... SiteLinks created between each site and the DataCentre with Default ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication & Logon question
    ... I assume these are not now direct connections but mean a ... replicate all DCs using the other replication ... I see, but the way your network is set up, the "guest" won't be able ... managing the group membership seems to be the ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication & Logon question
    ... I assume these are not now direct connections but mean a ... replicate all DCs using the other replication ... must be able to connect to that resource. ... managing the group membership seems to be the ...
    (microsoft.public.windows.server.active_directory)
  • Re: rpc servser not available
    ... The replication generated an error: ... From MAIL to <server> ... The DSA operation is unable to proceed because of a DNS lookup ... You must make sure there are no existing net use connections, ...
    (microsoft.public.windows.server.active_directory)
  • Re: How to stop two servers in different sites trying to replicate with each other
    ... communicate directly with Site C and vice versa. ... ADSS the DC in Site B keeps setting up one of its replication partners to ... ISTG for intersites connections using BH) ... the ISTG won't use the BH servers between Site C and ...
    (microsoft.public.win2000.active_directory)
Loading