Tips to Troubleshoot Lotus Notes Replication Issues – Ultimate Guide

Lotus Notes has the ability to synchronize the Notes data or documents from the single database but on the multiple servers (containing a local synchronized copy of the database) over time. This process of synchronization is known as replication. In this process, the special copy of the database is known as Replica through which users can exchange modification in the database. Whenever a single or more users edit the document and create a replica, there are chances of some conflicts like which document is a replica. Therefore, in this blog, multiple ways to troubleshoot Lotus Notes replication issues are discussed.

Two Types of Replication Processes Available in Lotus Notes

1. Server to Server: The replication process in which connection document and server console are necessary for initiating. It includes usage of the server’s replicator.
2. Workstation to Server: The replication process that let users read and work on the local replica. It does not include any use of server’s replicator.

Main Reasons Behind Lotus Notes Replication Issues

Whenever there is a replication issue in the Lotus Notes, there must be some proper reason behind it. This segment of the blog will discuss the same only:

• Schedule of Replication: It might be possible that incorrect scheduled date is mentioned in the connection document. This will result an error in replication.
• Type of Replication: There are four type of replication i.e., Push-Push, Pull-Pull, Push-only, and Pull-only. However, choosing any one from these four types can forbid the bidirectional replication.
• Access List of Server: If the server permission for replication is not granted, then also this replication procedure will not take place.
• Authentication: Before starting the replication, a handshaking process must be enabled between the all replication parties. It means there must be a common certificate shared between the parties. Otherwise, the replication will not take place.
• Replica ID: If the replica ID of the application is not identical then replication is not allowed.
• Replication Settings: If the replication setting is not enabled, a user is not allowed to replicate the database.
• ACL or Access Control List: If the desired server does not contain application for the ACL access on the server that needs to initiated, then it might be possible that few applications are not replicated properly.

How to Troubleshoot Lotus Notes Replication Error?

After understanding the factors that are responsible for the Lotus Notes replication issues, it is important to make the changes accordingly. Now, to do the same and set all those factors properly, follow the workarounds discussed below:

#1: Replication Schedule

1. First of all, open IBM Domino Administrator and move to Configuration tab
2. After that, choose Server and expand it from the left-hand side
3. Now, you have to open the connection document and choose the Schedule tab
4. Here, you can verify the schedule of replication i.e., it is enabled or not. If not, then simply enable it for the replication process.

#2: Type of Replication

1. To initiate the process, open IBM Domino Administrator
   2. Then, choose the Local and move to Replication/Routing tab directly
   3. Here, simply search for the Replication type box and there review the replication type
   4. Now, check if the replication type is correct or not (according to you). If not, click on the drag button and choose the appropriate type of replication. Click on the OK button.

#3: Server Access Field

1. First of all, open IBM Domino Administrator and choose Local
2. After that, choose Server option and expand it
3. Then, click on the Current Server Document and move to Security tab
4. Under the Security tab, just scroll the window down until you find Server Access Field and verify the targeted server name. If the desired server name is not displayed, mention the name by typing it correctly where you want to grant access to replicate.

#4: Authentication

1. To begin the process, open IBM Domino Administrator and click on the Configuration tab
2. After that, click on the Certification tab on the right-hand side of window and choose Cross Certify option
3. Here, you need to check each other server id i.e. targeted and source server id
4. If everything is perfect, click on the Cancel button. If not, update the details and click on the OK button.

#5: Replica ID

1. Initially, open Lotus Notes application on the local machine
2. After that, open Lotus Notes workspace where replication copy is available
3. Then, Right-click on the created replica and move to Application >> Properties
4. Next, move to i tab on the window and verify the replica id. You have to make sure that replica id and database id is identical.

#6: ACL

1. To start the process, open Lotus Notes application
2. Here, open the Lotus Notes workspace where copy of replication is available
3. After that, Right-click on the created replica and move to Application >> Access Control
4. Now, have a look at the targeted server that it is available or not. If not, click on the Add button for adding the server

Final Words

There are multiple types of replication issues faced by the users in Lotus Notes. Therefore, this blog will let users know about the different factors that create issues and how to troubleshoot these lotus notes replication issues.