Manage Learn to apply best practices and optimize your operations.

"NAB" your Domino directory problems before they spread

"NAB" your Domino directory problems before they spread

We are a large organization with fourteen divisions that are in the administrative sense "autonomous." Though I am the administrator for the National Home Office I do not have access to all of the servers in all of the divisions. Unfortunately this is true for some T2 servers.

Our address book has been victimized by corruption and mistakes made in the other divisions. Notifications don't always work especially with corruption. Because of this we came up with a replication topology just for the address book.

T2 ---> Pull only ---> NAB Server ---> Push only (manual) ---> T1 ---> Push only ---> T2

The T2 doesn't have access to pull from the NAB Server or push to the T1 server.

This could also work with other databases having content and replication issues.

Do you have comments on this tip? Let us know.

This tip was submitted to the tip exchange by member Leftoverkarma. Please let others know how useful it is via the rating scale below. Do you have a useful Notes/Domino tip or code to share? Submit it to our monthly tip contest and you could win a prize and a spot in our Hall of Fame.

Dig Deeper on Lotus Domino Directory

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.




  • iSeries tutorials's tutorials provide in-depth information on the iSeries. Our iSeries tutorials address areas you need to know about...

  • V6R1 upgrade planning checklist

    When upgrading to V6R1, make sure your software will be supported, your programs will function and the correct PTFs have been ...

  • Connecting multiple iSeries systems through DDM

    Working with databases over multiple iSeries systems can be simple when remotely connecting logical partitions with distributed ...