Table of Contents
Advertisement
Note that if you have configured replication agreements to always keep the
supplier server and the consumer server in sync, this is not sufficient to bring back
up-to-date a server that has been offline for over five minutes. The reason is that
with the "Always Keep in Sync" option, the server generates a replication
operation for every update operation it processes. However, if this replication
operation cannot be performed because the consumer is offline, the operation times
out after 10 minutes.
NOTE
The procedures described in this section can only be used when
replication is already set up, and consumers have been initialized.
To ensure that directory information will be synchronized immediately when a
server comes back online, you can use either the Directory Server Console on the
supplier server that holds the reference copy of the directory information or a
customizable script.
Forcing Replication Updates From the Console
To ensure that replication updates are sent immediately when a consumer or a
supplier in a multi-master replication configuration comes back online after a
period of time, you can perform these steps on the supplier server that holds the
most recent version of the directory information:
On the Directory Server Console, click the Configuration tab, expand the
1.
Replication folder and the database nodes until you select the replication
agreement corresponding to the replica that you must update.
Right click the replication agreement, and choose Send Updates Now from the
2.
drop-down list.
This initiates replication toward the server that holds the information that
needs to be updated.
Forcing Replication Updates From the
Command Line
From the consumer that requires updating, you can run a script that prompts the
supplier to send replication updates immediately. This script is shown in Code
Example 8-1.
Forcing Replication Updates
Chapter 8
Managing Replication
317
Advertisement
Table of Contents
Troubleshooting
