Forcing a full database replication

You can use the Replicate command with the -F option to force a full database replication when replicas of a database get out of sync. The replication occurs on the side and allows users to continue to see replication updates during the full replication.

About this task

This method is an alternative to clearing the database replication history. For large databases, clearing the replication history to force a full replication can take time and delay the replication of new updates until it is complete. For example, if you clear the replication history of a mail file, the user might not see new mail until the full replication completes.


To force a full replication, use the following server command:
Replicate <server> <database> -F

Use the -L option to log details about the documents (notes) that would replicate if you use the -F option but without actually performing the replication. For example:
Replicate Mail\Renovations mail/sdaryn.nsf -L
Output similar to the following is shown. >>> Indicates a description for this documentation that is not shown in the output.
[4894:0002-0748] NoteRepl: CN=Mail\O=Renovations!!mail/sdaryn.nsf to mail/sdaryn.nsf Since 07/27/2018 08:25:22 AM
>>>Replicating from remote replica (sdaryn) to local replica (pull).  Since=The replication history from last pull 
[4894:0002-0748] 07/27/2018 08:28:57 AM  Starting replication with server Mail\Renovations
[4894:0002-0748] 07/27/2018 08:28:57 AM  Pulling mail\sdaryn.nsf from Mail\Renovations mail/sdaryn.nsf
[4894:0002-0748] NoteRepl: UNID 7235FD43:BB0874BA:852582A2:0052CF6C Cls 1
>>> UNID and Cls=NoteClass
[4894:0002-0748]     Src: NID A96 SN 2 ST 07/27/2018 08:15:07 AM Mod: 07/27/2018 08:15:07 AM

>>> Source note info (in this case the source is the remote replica), NID=NoteID, SN=Sequence number, ST=Sequence time, Mod=Modified time
[4894:0002-0748]     Dest: NID 0 SN 0 ST  Did not repl

>>> Destination note info.  "Did not repl" means that it should have replicated in the past, but the note is missing from the destination (local) replica.
[4894:0002-0748] NoteRepl: mail/sdaryn.nsf to CN=Mail\O=Renovations!!mail/sdaryn.nsf Since 07/27/2018 08:25:23 AM

>>> Replicating from local to remote. Since=Replication history from last push
[4894:0002-0748] 07/27/2018 08:28:57 AM  Pushing mail/sdaryn.nsf to Mail\Renovations mail/sdaryn.nsf
[4894:0002-0748] NoteRepl: UNID 29BD9D7B:04808407:852582A2:0052CF6E Cls 1
[4894:0002-0748]     Src: NID A9E SN 2 ST 07/27/2018 08:28:43 AM Mod: 07/27/2018 08:28:43 AM
[4894:0002-0748]     Dest: NID A9E SN 1 ST 06/04/2018 11:04:35 AM Waiting to repl

>>> "Waiting to repl" means that this note will replicate the next time the databases replicate.  Nothing wrong here.

[4894:0002-0748] 07/27/2018 08:28:57 AM  Finished replication with server Mail\Renovations
[4894:0002-0748] 07/27/2018 08:28:57 AM  Database Replicator shutdown