Problem solve Get help with specific problems with your technologies, process and projects.

Replication best practices for Lotus Domino disaster recovery

When using Lotus Notes database replication for disaster recovery purposes, find out what data you need to include for full recoveries.

I'd like to know what the best practice is to accomplish Lotus Notes database replication for disaster recovery purposes -- is it a cold standby? In the case of disaster, I want to set up a new Lotus Domino server, and then build Lotus Domino with a replicated database. In this scenario, what is the data we MUST replicate?

Also, I have been monitoring disk activity for our Lotus Domino server, and found that the data change rate is very high during compact and the fix-up task. Do you know any way to reduce the changes?

What data you need is wholly dependant on what is deemed critical. From a Lotus Domino perspective, names.nsf is the only "necessary" database. Other directories and mission-critical applications should also be considered, as well as key mail files and the like. You will need separately stored server ID files, Notes.ini files and the like, since those do not replicate.

As for the disk activity, there is nothing you can do. Those tasks are extremely disk-intensive, because they are either copying data, querying data, or rearranging it. The only thing you can try is to limit those activities to off-hours via program documents.

Do you have comments on this Ask the Expert Q&A? Let us know.

Related information from

Dig Deeper on Lotus Notes Domino Replication and Synchronization

  • Favorite iSeries cheat sheets

    Here you'll find a collection of valuable cheat sheets gathered from across the iSeries/ community. These cheat ...