Write and replicated write messages

Edit online

To identify replication conflicts and related issues, you must understand the difference between write and replicated write messages.

In an IBM® Verify Directory environment, you might see informational message, such as

GLPSRV202I During the last hour 40 updates were received from suppliers 
and 10 updates were received from other clients.

This message in the ibmslapd.log file indicates that a directory server is participating as a peer server in a replication network of directory servers. A peer server can receive updates from other peer servers and from client applications. A stand-alone master server shows zero updates from other suppliers. However, it can have some updates from clients, which depend on the update activity in a specified hour. A directory server that is configured only as a replica shows some updates from suppliers and zero updates from clients. Updates that are sent to such a replica that were referred to a master server are not counted as updates from clients.

The message that shows updates from suppliers and clients can serve as a possible informational message to indicate that replication conflicts might occur. There can also be cases where the updates from clients and suppliers are for entries in different replication contexts and no conflicts might occur. Depending on the replication topology it is also possible that updates from clients are being routed to different master servers configured as peers. This process has the potential for causing conflicts, particularly when the updates are for groups. Replication conflict resolution ensures that the data across the multiple servers converges, but some updates are overwritten. It is advisable to have updates for a particular replication context sent to a single server even when peer servers are available.