Re: Active Directory 2003: Intra-Site Replication of Schema Partit



So what is normal intrasite notification then?

It is my understanding by default that a Windows 2003 domain has a 15 second
latency before it will notify a partner DC of changes. So, you can see from
my repadmin results that the schema partition is getting updated from the hub
to the bridgehead but it isn't getting updated from the bridgehead to the
second DC. Is that normal? I know there is a default setting to intra-site
replicate at least every 60 minutes, if the partition hasn't been updated. So
is inter-site updating every 15 minutes all paritions, changes or not, but
intra-site replicaiton only replicating of there are changes in the partition
or 60 minutes?

"Jorge Silva" wrote:

according with your repadmin results, you have 2 DCs in the Branch-Site
(BranchDC01, BranchDC02)
BranchDC01 is the BH server and that server is the server that replicates
with other BH servers in different Site(s).
BranchDC02 will follow the normal intrasite replication as normal.

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"MSBob69" <MSBob69@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9834475C-A38A-4C39-AB4D-E48615513CA7@xxxxxxxxxxxxxxxx
C:\>repadmin /showrepl BranchDC02
Branch-Site\BranchDC02
DC Options: IS_GC
Site Options: (none)
DC object GUID: 9b3fc67b-bfe8-4720-a6dd-c5bb66f2bb05
DC invocationID: 176cad1c-aa44-4784-9a31-d4d4945d5d9d

==== INBOUND NEIGHBORS ======================================

DC=MyDomain,DC=local
Branch-Site\BranchDC01 via RPC
DC object GUID: 0b9beabe-4520-4fb4-b362-e023b2e8c5ad
Last attempt @ 2007-09-11 10:47:09 was successful.

CN=Configuration,DC=MyDomain,DC=local
Branch-Site\BranchDC01 via RPC
DC object GUID: 0b9beabe-4520-4fb4-b362-e023b2e8c5ad
Last attempt @ 2007-09-11 10:32:03 was successful.

CN=Schema,CN=Configuration,DC=MyDomain,DC=local
Branch-Site\BranchDC01 via RPC
DC object GUID: 0b9beabe-4520-4fb4-b362-e023b2e8c5ad
Last attempt @ 2007-09-11 10:01:00 was successful.


C:\>repadmin /showrepl BranchDC01
Branch-Site\BranchDC01
DC Options: IS_GC
Site Options: (none)
DC object GUID: 0b9beabe-4520-4fb4-b362-e023b2e8c5ad
DC invocationID: 8541a013-4582-4589-a47b-80e5b7598031

==== INBOUND NEIGHBORS ======================================

DC=MyDomain,DC=local
TMobile-West\HubDC02 via RPC
DC object GUID: 826c2a05-6bde-4577-8e57-12cfe3bd5c8e
Last attempt @ 2007-09-11 10:46:49 was successful.
Branch-Site\BranchDC02 via RPC
DC object GUID: 9b3fc67b-bfe8-4720-a6dd-c5bb66f2bb05
Last attempt @ 2007-09-11 10:48:11 was successful.

CN=Configuration,DC=MyDomain,DC=local
Branch-Site\BranchDC02 via RPC
DC object GUID: 9b3fc67b-bfe8-4720-a6dd-c5bb66f2bb05
Last attempt @ 2007-09-11 10:46:49 was successful.
TMobile-West\HubDC02 via RPC
DC object GUID: 826c2a05-6bde-4577-8e57-12cfe3bd5c8e
Last attempt @ 2007-09-11 10:46:50 was successful.

CN=Schema,CN=Configuration,DC=MyDomain,DC=local
Branch-Site\BranchDC02 via RPC
DC object GUID: 9b3fc67b-bfe8-4720-a6dd-c5bb66f2bb05
Last attempt @ 2007-09-11 10:46:49 was successful.
TMobile-West\HubDC02 via RPC
DC object GUID: 826c2a05-6bde-4577-8e57-12cfe3bd5c8e
Last attempt @ 2007-09-11 10:46:50 was successful.


C:\>repadmin /replsummary /bysrc /bydest /sort:delta
Replication Summary Start Time: 2007-09-11 10:48:56

Beginning data collection for replication summary, this may take awhile:
......................................


Source DC largest delta fails/total %% error
BranchDC01 47m:56s 0 / 3 0
BranchDC02 10m:23s 0 / 6 0
HubDC02 09m:44s 0 / 13 0

Destination DC largest delta fails/total %% error
BranchDC02 48m:35s 0 / 3 0
BranchDC01 02m:42s 0 / 6 0
HubDC02 :18s 0 / 10 0


So after 60 minutes The BranchDC02 will automatically sync the schema
partition which is what I expect. But since adding the second domain
controller to branch-site, repadmin /replsummary is always 50+ minutes but
before that it was never over 15 minutes. When I demote the second domain
controller, things go back to 15 minutes. So, do I have a problem or is
this
normal?

"Jorge Silva" wrote:

Hi
What do you meant with no replication schema?
Any errors in event log?
can you post the results for the repadmin cmd.

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"MSBob69" <MSBob69@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4082CECE-4BB3-4798-8869-763D80D33B09@xxxxxxxxxxxxxxxx
I have AD 2003 with about 10 domain controllers. I have two hubs with
two
domain controllers which change notification turned on. The rest are in
remote locations, one per location, and replicate changes every 15
minutes.
I have location where I added a second domain controller. I have a
script
I
run daily that runs repadmin /replsummary. Since I added the second
domain
controller my repadmin /repsummary has gone from 15 minutes to 55-60
minutes.
I know that by default AD will replicate every 60 minutes. By looking
at
repadmin /showrepl I see that the schema not replicating but the other
partitions are from the bridgehead to second DC. Is this normal. All
the
tests, dcdiag, netdiag, etc., I run don't show any errors?






.



Relevant Pages

  • Re: Active Directory 2003: Intra-Site Replication of Schema Partit
    ... Check your site links to make sure you replicate interval is less than hour. ... repadmin /showreps ... Branch-Site\BranchDC01 via RPC ... But since adding the second domain ...
    (microsoft.public.windows.server.active_directory)
  • Re: The remote procedure call was cancelled.
    ... RPC needs high ports>1024. ... All the servers are connected to central HUB (four ... When we try to replicate the naming context ...
    (microsoft.public.windows.server.active_directory)
  • Re: Creating a Child Domain OFFLINE
    ... > Site A exists and is the forest domain controller. ... Since connectivity between sites B & C may not ... > Leave it there long enough to replicate all the domain info. ...
    (microsoft.public.windows.server.active_directory)
  • DCPromo - replication failed "Directory Object not found"
    ... FOREST: bigad.local (AD Zone DNS) ... If this is a replica domain controller, ... Source domain controller address: ... This domain controller will be unable to replicate with the source domain ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replicate only 1 OU to another Domain Controller;
    ... and discuss with them about their service offering for hosters. ... > UPN suffixes all under our one main domain on Windows Server 2003 AD. ... > controller at that company's site office with DFS so they can work on the ... > files locally but we don't want all the other OU's to replicate to it as ...
    (microsoft.public.windows.server.active_directory)