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 SearchDomino.com:
- Tip: Lotus Notes/Domino replication primer for administrators
- Reference Center: Notes/Domino administration
- Reference Center: Notes/Domino database backup
Dig Deeper on Lotus Notes Domino Replication and Synchronization
Related Q&A from Michael Lazar
Learn how to easily keep track of the numbers of incoming and outgoing Lotus Notes email messages to and from your Domino server each day. Continue Reading
Discover what steps you can take if your Lotus Domino server runs out of disk space and you have issues sending and receiving Lotus Notes email ... Continue Reading