Force AD replication w/repadmin

  • Thread starter Thread starter Harald Bilke
  • Start date Start date
H

Harald Bilke

Hi fellas,

during some test (be prepared...) I'd like to force a replication like
described at the W2k3 Server Tech-Ref Examples for repadmin:

[beginquote]
Example 2: Force a replication event between two replication partners

The following example uses the replicate operation of RepAdmin to
force the domain directory partition for microsoft.com on Server1 to
replicate with the domain directory partition on Server2. This makes
Server2 the source and Server1 the destination server.

The required parameters for the replicate operation are the name of
the server that will receive changes (DestDC in the syntax), the name
of the directory partition (NamingContext in the syntax), and the
objectGUID of the directory partition that will send the changes
(SourceDCUUID in the syntax).

Type the following at the command prompt:

repadmin /replicate server2.microsoft.com server1.microsoft.com dc=
rktlabdom,dc=com

Press Enter and the following output is displayed:


server2.microsoft.com
Sync from server1.microsoft.com to server2.microsoft.com completed
successfully.

[endquote]

Two Q.s:
a) Shouldn't the "dc= rktlabdom" in the given example/command be
"dc=microsoft"?

b) Will "server2" get all the data from "server1" even if the
tombstone-limit has been reached or other events do apply that stopped
replication?


Thanx in advance
Harald
 
a) Shouldn't the "dc= rktlabdom" in the given example/command be
"dc=microsoft"?
Click to expand...

Yes, that would make things more clear. It's possible to have a different
DNS namespace and domain name, but generally not recommended, and only
complicates things when using illustrations that aren't specific to that
setup.

b) Will "server2" get all the data from "server1" even if the
tombstone-limit has been reached or other events do apply that stopped
replication?
Click to expand...

No. Once the tombstone lifetime has expired, replication should fail, and
an event be logged. I believe there can be instances whereby things
replicate. But generally once the lifetime has exceeded there is only one
option: demote, cleanup and promote the box.


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

Hi fellas,

during some test (be prepared...) I'd like to force a replication like
described at the W2k3 Server Tech-Ref Examples for repadmin:

[beginquote]
Example 2: Force a replication event between two replication partners

The following example uses the replicate operation of RepAdmin to
force the domain directory partition for microsoft.com on Server1 to
replicate with the domain directory partition on Server2. This makes
Server2 the source and Server1 the destination server.

The required parameters for the replicate operation are the name of
the server that will receive changes (DestDC in the syntax), the name
of the directory partition (NamingContext in the syntax), and the
objectGUID of the directory partition that will send the changes
(SourceDCUUID in the syntax).

Type the following at the command prompt:

repadmin /replicate server2.microsoft.com server1.microsoft.com dc=
rktlabdom,dc=com

Press Enter and the following output is displayed:


server2.microsoft.com
Sync from server1.microsoft.com to server2.microsoft.com completed
successfully.

[endquote]

Two Q.s:
a) Shouldn't the "dc= rktlabdom" in the given example/command be
"dc=microsoft"?

b) Will "server2" get all the data from "server1" even if the
tombstone-limit has been reached or other events do apply that stopped
replication?


Thanx in advance
Harald
 
Hi/2

Yes, that would make things more clear. It's possible to have a different
DNS namespace and domain name, but generally not recommended, and only
complicates things when using illustrations that aren't specific to that
setup.
Click to expand...

Thanx!
And I've found "microsoft" at some of the other examples...
No. Once the tombstone lifetime has expired, replication should fail, and
an event be logged. I believe there can be instances whereby things
replicate. But generally once the lifetime has exceeded there is only one
option: demote, cleanup and promote the box.
Click to expand...

But not a big problem b4 tombstone, right?

Thanx for answering
 
But not a big problem b4 tombstone, right?

That's right! Before the tombstone period is fine - normal replication will
occur. If there's lots of changes, and nothings replicated in a while it
can take a couple of minutes though ;-)

Thanx for answering
Click to expand...

No problem at all!

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

Hi/2

Yes, that would make things more clear. It's possible to have a different
DNS namespace and domain name, but generally not recommended, and only
complicates things when using illustrations that aren't specific to that
setup.
Click to expand...

Thanx!
And I've found "microsoft" at some of the other examples...
No. Once the tombstone lifetime has expired, replication should fail, and
an event be logged. I believe there can be instances whereby things
replicate. But generally once the lifetime has exceeded there is only one
option: demote, cleanup and promote the box.
Click to expand...

But not a big problem b4 tombstone, right?

Thanx for answering
 
Back
Top