I think we typically talk about CO and naming context because that is how the replication takes place isn't it? (#3?)
When you get down to it, the actual replication queue item is NC based, not connection based. If you force it to replicate a specific connection (ala sites and services tool) it will queue up requests to replicate every naming context handled by that connection. The other methods of queuing replication is when a DC received a change notification then it will pull that specific NC from the DC that sent the change notification, not everything on that CO. However when the timer runs out for a intersite replication a queue item will be popped for every NC each CO is responsible for. At least this is what I see when I watch the inbound queue. joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Fleischman Sent: Saturday, May 15, 2004 4:56 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Last Replication Occurrence Sure, so long as you understand the caveats: 1) A DC doesn't initiate replication wholesale so much as it does initiate replication on a particular connection object (a CO is the "connection" so to speak between two DCs from a replication perspective). 2) Replication is inbound from a CO perspective....when you say that replication took place over a given CO that means it was inbound from dc1 to dc2. 3) We typically talk about replication not only on a per CO basis but also on a per naming context perspective. You can run repadmin /showreps against a DC to see the status of its inbound replication objects as well as replication notifications of partners. That's what many people do as a first view of a specific DC. My favorite way of viewing replication uses a switch that, if memory serves me correctly, was added in 2k03's repadmin: repadmin /showrepl * /csv That lets me see the status of inbound replication on all COs for all NCs on all DCs in the forest. For a single naming context, repadmin /showutdvec is really nice too, but that doesn't show each CO, it just shows a replication "summary" of sorts from the perspective of a given DC, taken from the up to dateness vector. This command isn't as interesting until forest functional level is >=1 as we don't time-stamp the utdv until we attain that level of functionality. ~Eric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Adner Sent: Saturday, May 15, 2004 2:54 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] Last Replication Occurrence I know repadmin /showmeta will tell me when an object was last updated, but is there a switch (or other command) to just show when replication was last initiated on a Dc, regardless if anything was actually replicated or not? I know I can enable more logging for the NTDS service, but I'm curious if there's an easier method available. Thx List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
