Friday, 9 November 2018

Domino 10 - Synchronize Database Replicas - New Option Replicate Command


This last blog post concerning the new IBM Domino 10 Administrator features  is meant purely for my own documentation in case I need the new replicate command in the near future. In IBM Domino 10 there is a new option for the Replicate command for Domino Administrators, -F, to force a full database replication when replicas of a database get out of sync. The replication takes place on the side and allows users to continue to see replication updates during the full replication. Administrators can use  the -L argument to log information about the documents (notes) that would replicate if the new option -F is used but without actually performing the replication. Until now the only option for Administrators to perform a full replication of content was by clearing the replication history. Be aware that for large databases a full replication can take time and delay the replication of new updates until it is complete. For example if the replication history of a mail file is cleared the mail user might not see new mail until the full replication completes.

To force a full replication Administrators can now use the following server command: replicate <server> <database> -F.
Example: replicate MS-DOMINO10/ALM mail\jdomino.nsf -F

Administrators can use the -L option to log details about the documents (notes) that would replicate if the -F option is used but without actually performing the replication. For example: replicate MS-DOMINO10/ALM mail\jdomino.nsf -L

Since I currently not have any replica's out of sync I don't get all the output as mentioned in the IBM documentation as shown below. Based on the new replicate command -F and the -L option to log details the output will look something like this on the Domino console.

[17F8:0002-1028] NoteRepl: CN=Mail\O=MSDOMINO10!!mail/jdomino.nsf to mail/jdomino.nsf Since 07/27/2018
 Replicating from remote replica (jdomino) to local replica (pull). Since = The replication history from 
[17F8:0002-1028]  07-11-2018 08:28:57 Starting replication with server Mail\MSDOMINO10
[17F8:0002-1028]  07-11-2018 08:28:57 Pulling mail\jdomino.nsf from Mail\MSDOMINO10 mail/jdomino.nsf
[17F8:0002-1028] NoteRepl: UNID 7235FD43:BB0874BA:852582A2:0052CF6C Cls 1
UNID and Cls = NoteClass
[17F8:0002-1028] Src: NID A96 SN 2 ST 07-11-2018 08:15:07  Mod: 07-11-2018 8:15:07
Source note info (in this case the source is the remote replica), NID = NoteID, SN = Sequence number
[17F8:0002-1028] 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 [17F8:0002-1028] NoteRepl: mail/jdomino.nsf to CN=Mail\O=MSDOMINO10!!mail/jdomino.nsf Since 07-11-2018 Replicating from local to remote. Since = Replication history from last push
[17F8:0002-1028] 07-11-2018 08:28:57  Pushing mail/jdomino.nsf to Mail\MSDOMINO10 mail/jdomino.nsf
[[17F8:0002-1028] NoteRepl: UNID 29BD9D7B:04808407:852582A2:0052CF6E Cls 1
[17F8:0002-1028] Src: NID A9E SN 2 ST 07-11-2018 08:28:43  Mod: 07-11-2018 08:28:43
[17F8:0002-1028] Dest: NID A9E SN 1 ST 12-10-2018 11:04:35 Waiting to repl
"Waiting to repl" means that this note will replicate the next time the databases replicate. [17F8:0002-1028] 07-11-2018 08:28:57 Finished replication with server Mail\Renovations
[17F8:0002-1028] 07-11-2018 08:28:57 AM Database Replicator shutdown

Another great new IBM Domino 10.0 Administrator feature. In my next blog post more about advanced search capabilities and query definitions in Notes databases using LotusScript.

No comments:

Post a Comment