replication

R

Ryan Rinehart

Hello!

I have been using repadmin to try to determine if my replication is working
properly. I am using the version from 2003 support tools on my xp client on
a 2000 domain. I am running the following command

REPADMIN /REPLSUM /BYSRC /BYDEST /SORT:DELTA

Is there any baseline you should see in the results here? My largest delta
fluctuates from 13m up to 1h+. We had some replication collisions in our
root domain and now I am trying to verify everything is working correctly.
Is anyone familiar with what output i SHOULD be seeing using this command?

Thanks,

Ryan Rinehart
 
E

Eric Fleischman [MSFT]

*big breath*
Depends, maybe, kinda sorta, well, I dunno. :)
It's very hard to answer a question like this. It is highly dependent upon
your environment, how the sites and site links are set up, and what OS
everyone is running.

From a high level, as long as things stay fairly consistent and you are
happy with performance, life is ok. Of course checking the DS event logs is
key and you want to make sure we're not getting errors there (KCC errors,
replication errors, etc).

My bet would be that, as long as the values stay fairly constant and your
logs are clean, you're ok. If you see 1hour become 2, then 3, then 24, etc.
then you probably have something to look in to.

Without fine details about your environment and some study and running a lot
of tools, I couldn't really give you more details i'm afraid.

Sorry I couldn't answer this more precisely.
~Eric
 
R

Ryan Rinehart

Thanks Eric.

Our site links are setup with 15 minutes between reps. I was reading this
article

http://support.microsoft.com/default.aspx?scid=kb;EN-US;325379

and it says :

Use the Windows Server 2003 version of Repadmin.exe on a Windows XP- or
Windows Server 2003-based member computer in the forest with the following
arguments:
REPADMIN /REPLSUM /BYSRC /BYDEST /SORT:DELTA <-output formatted
to fit on page

DestDC largest delta fails/total %% error

NA-DC-01 13d.21h:10m:10s 97 / 143 67 (8240) There is no such object...
NA-DC-02 13d.04h:11m:07s 180 / 763 23 (8524) The DSA operation...
NA-DC-03 12d.03h:54m:41s 5 / 5 100 (8524) The DSA operation...
All the domain controllers in the forest must replicate without
error and the value in the "Largest Delta" column must not be greater than
the replication frequency that the matching site link or connection object
define. Investigate any domain controllers in the REPLSUM output that is
reporting replication errors, especially those that have not replicated
inbound or outbound changes in Tombstone Lifetime (TSL) number of days (by
default, 60 days). To do so, view the output from repadmin /showrepl * /CSV
c:\repldrilldown.csv in an electronic spreadsheet program that imports .csv
files, and then sort on the "last success time".

Be careful when you try to resolve replication errors on domain controllers
that have not replicated inbound or outbound changes for a naming context
for greater than tombstonelifetime number of days. When you do so, you may
reanimate objects that were deleted on one domain controller but are still
active on other domain controllers if knowledge of the deletion did not
fully propagate throughout the forest in the previous 60 days.


Since all my site links are set to 15 minutes, I was getting nervous that
something is wrong. Maybe I need to adjust my site link replication
interval?


Eric Fleischman said:
*big breath*
Depends, maybe, kinda sorta, well, I dunno. :)
It's very hard to answer a question like this. It is highly dependent upon
your environment, how the sites and site links are set up, and what OS
everyone is running.

From a high level, as long as things stay fairly consistent and you are
happy with performance, life is ok. Of course checking the DS event logs is
key and you want to make sure we're not getting errors there (KCC errors,
replication errors, etc).

My bet would be that, as long as the values stay fairly constant and your
logs are clean, you're ok. If you see 1hour become 2, then 3, then 24, etc.
then you probably have something to look in to.

Without fine details about your environment and some study and running a lot
of tools, I couldn't really give you more details i'm afraid.

Sorry I couldn't answer this more precisely.
~Eric

--
Eric Fleischman [MSFT]
Directory Services
This posting is provided "AS IS" with no warranties, and confers no rights.


Ryan Rinehart said:
Hello!

I have been using repadmin to try to determine if my replication is working
properly. I am using the version from 2003 support tools on my xp
client
on
a 2000 domain. I am running the following command

REPADMIN /REPLSUM /BYSRC /BYDEST /SORT:DELTA

Is there any baseline you should see in the results here? My largest delta
fluctuates from 13m up to 1h+. We had some replication collisions in our
root domain and now I am trying to verify everything is working correctly.
Is anyone familiar with what output i SHOULD be seeing using this command?

Thanks,

Ryan Rinehart
 
E

Eric Fleischman [MSFT]

Probably not......I'd be ok with that value so long as it hovered and didn't
go up substantially.
If it starts climbing, that is reason for concern.

~Eric


--
Eric Fleischman [MSFT]
Directory Services
This posting is provided "AS IS" with no warranties, and confers no rights


Ryan Rinehart said:
Thanks Eric.

Our site links are setup with 15 minutes between reps. I was reading this
article

http://support.microsoft.com/default.aspx?scid=kb;EN-US;325379

and it says :

Use the Windows Server 2003 version of Repadmin.exe on a Windows XP- or
Windows Server 2003-based member computer in the forest with the following
arguments:
REPADMIN /REPLSUM /BYSRC /BYDEST /SORT:DELTA <-output formatted
to fit on page

DestDC largest delta fails/total %% error

NA-DC-01 13d.21h:10m:10s 97 / 143 67 (8240) There is no such object...
NA-DC-02 13d.04h:11m:07s 180 / 763 23 (8524) The DSA operation...
NA-DC-03 12d.03h:54m:41s 5 / 5 100 (8524) The DSA operation...
All the domain controllers in the forest must replicate without
error and the value in the "Largest Delta" column must not be greater than
the replication frequency that the matching site link or connection object
define. Investigate any domain controllers in the REPLSUM output that is
reporting replication errors, especially those that have not replicated
inbound or outbound changes in Tombstone Lifetime (TSL) number of days (by
default, 60 days). To do so, view the output from repadmin /showrepl * /CSV
c:\repldrilldown.csv in an electronic spreadsheet program that imports
..csv
files, and then sort on the "last success time".

Be careful when you try to resolve replication errors on domain controllers
that have not replicated inbound or outbound changes for a naming context
for greater than tombstonelifetime number of days. When you do so, you may
reanimate objects that were deleted on one domain controller but are still
active on other domain controllers if knowledge of the deletion did not
fully propagate throughout the forest in the previous 60 days.


Since all my site links are set to 15 minutes, I was getting nervous that
something is wrong. Maybe I need to adjust my site link replication
interval?


Eric Fleischman said:
*big breath*
Depends, maybe, kinda sorta, well, I dunno. :)
It's very hard to answer a question like this. It is highly dependent upon
your environment, how the sites and site links are set up, and what OS
everyone is running.

From a high level, as long as things stay fairly consistent and you are
happy with performance, life is ok. Of course checking the DS event logs is
key and you want to make sure we're not getting errors there (KCC errors,
replication errors, etc).

My bet would be that, as long as the values stay fairly constant and your
logs are clean, you're ok. If you see 1hour become 2, then 3, then 24, etc.
then you probably have something to look in to.

Without fine details about your environment and some study and running a lot
of tools, I couldn't really give you more details i'm afraid.

Sorry I couldn't answer this more precisely.
~Eric

--
Eric Fleischman [MSFT]
Directory Services
This posting is provided "AS IS" with no warranties, and confers no rights.


Ryan Rinehart said:
Hello!

I have been using repadmin to try to determine if my replication is working
properly. I am using the version from 2003 support tools on my xp
client
on
a 2000 domain. I am running the following command

REPADMIN /REPLSUM /BYSRC /BYDEST /SORT:DELTA

Is there any baseline you should see in the results here? My largest delta
fluctuates from 13m up to 1h+. We had some replication collisions in our
root domain and now I am trying to verify everything is working correctly.
Is anyone familiar with what output i SHOULD be seeing using this command?

Thanks,

Ryan Rinehart
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top