USER AND SERVER CONFIGURATION


Forcing immediate replication
You can replicate changes to critical databases, such as the IBM® Lotus® Domino® Directory, without waiting for a scheduled connection. After you create Connection documents to schedule server-to-server replication, you can use a server command to force immediate replication.

There are many situations when forcing replication is necessary. For example, you may want to update a database immediately, without waiting for scheduled replication to occur, or you might need to replicate with a different server because the usual server is unavailable. You can force immediate replication to trace replication and mail routing problems or to force changes to critical system databases -- such as in the Domino Directory -- to spread quickly through the domain. When you force immediate server-to-server replication, you can initiate replication in one or in both directions.
CommandResult
Replicate Replicates changes to databases in both directions; Domino performs Pull-Push replication.
Pull Replicates changes to databases in one direction where the initiating server pulls changes from the other server.
Push Replicates changes to databases in one direction where the initiating server pushes database changes to the other server.
Related topics