Forcing Replication Updates - Red Hat DIRECTORY SERVER 7.1 - ADMINISTRATOR Administrator's Manual

Forcing Replication Updates

Stop the destination Directory Server if it is running by typing the following:
10.
On the destination server, restore the archives with the
11.
the optional
parameter is similar to the
Restart the destination Directory Server by typing the following:
12.
Replication will begin on schedule as soon as the destination server is restarted.
For more information on using these scripts, see the Red Hat Directory Server
Configuration, Command, and File Reference.
Forcing Replication Updates
When you stop a Directory Server involved in replication for regular
maintenance, when it comes back online, you need to ensure that it gets updated
through replication immediately. In the case of a supplier in a multi-master
environment, the directory information needs to be updated by the other supplier
in the multi-master set. In other cases, when a hub supplier or a dedicated
consumer is taken offline for maintenance, when they come back online, they
need to be updated by the supplier server.
If you have configured replication agreements to keep the supplier server and the
consumer server in sync always, 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
350 Red Hat Directory Server Administrator's Guide • May 2005
./stop-slapd
parameter to specify the backend instance name. This
-n
./bak2db
/opt/redhat-ds/servers/slapd-
userRoot
./start-slapd
The procedures described in this section can only be used when
replication is already set up and consumers have been initialized.
used with
-n ldif2db
serverID
script, using
bak2db
and . For example:
db2ldif
/archiveDirectory -n
-n