Usability - Productivity - Business - The web - Singapore & Twins

Golden Rules for Domino Adminstrators (courtesy of Manfred Meise)

Manfred Meise of MMI Consult has compiled a list of Golden Rules/ Administrative Pledges for Notes/Domino administrators. To save English readers the trouble of Google English I've translated (and amended) them for you:

The trouble free operation of a Notes/Domino infrastructure requires attention to (and observance of) a few basic rules. Or put it different: Ignoring or violating these rules is asking for trouble. The list doesn't claim to be complete and will (based on sad experience in projects) be extended in future.

As as responsible Lotus Domino Administrator I pledge the following:

  1. Never ever allow two replicas of a database to be stored on the same server
  2. Never ever use operating system tools to manipulate (copy, delete, rename or create) Domino databases. This includes using FTP to move databases to other locations!
  3. Never restore a Notes database directly to the server where it came from (unless the original is gone) - See also #1
  4. Always use the server console for unscheduled replications. Never use the client replicator page for that
  5. When using the transaction log always use a physically separate disk with sufficient space
  6. When using "archiving" transaction logging, ensure that the backup software does support this
  7. To create databases from templates always use File -Application... New.. Never copy or rename files on the OS level
  8. When creating DIR links always point them to destinations outside the Domino data directory. Never point two dir links to the same destination
  9. Neither install a Notes client on a Domino server, nor run the client part of the Domino server
  10. Set "Use operating system time" (including DST) on all clients and servers
  11. Ensure a proper backup. Replication (even cluster replication) is no replacement for backup
  12. Keep the servers running especially at night, so the house keeping functions can run
  13. Remove replicas from servers that have been offline for extended periods of time (e.g. 6 weeks) and fetch new replicas
  14. Replicate all system databases at least once a day (that includes: ensure the system databases are replicas)
  15. Never grant manager access to servers from other domains
  16. Always ensure system templates are the highest release of Domino servers in use. Templates are backwards, not forward compatible
  17. When using OS level virus scanners exclude at least the data directory. In a multi-user (client) install exclude all data directories of all users, at least *.nsf, *.ntf, *.box
  18. Every Domino server will be protected by a Domino aware virus scanner that can check the database content including the attachments
  19. Only run the server tasks that are in use and ensure proper configuration (keep in mind: some tasks like statistics and adminp are not "used" by users but still relevant)
  20. Never ever delete a person document when user leave. Always use the adminp process to ensure complete removal and addition to a deny-access group
  21. Never to use backup copies of ID files when users forget their password. Use IDVault and password recovery
  22. Ensure that users' workstations have the current set of drivers (first and foremost video) installed
  23. Fight disk fragmentation by regularly defragmenting Notes and Domino program and data drives
Thank you Martin!

Posted by on 21 December 2010 | Comments (6) | categories: Show-N-Tell Thursday


  1. posted by Sriram on Wednesday 22 December 2010 AD:
    Good list. It would have been better if you have said why I should not do them - how will it impact..like that Emoticon smile.gif
  2. posted by Stephan H. Wissel on Wednesday 22 December 2010 AD:
    @Sriram: Good idea, I might pickup the different topics as separate posts and elaborate on them -- quite a number of them (e.g. disk fragmentation) have been covered here or elsewhere, so it is a question of adding some links.

    Any specific topic you wonder about?
  3. posted by Sriram on Wednesday 22 December 2010 AD:
    Thanks for a quick response!!

    #2, #4, #21
  4. posted by Kalaivani on Friday 31 December 2010 AD:
    Hi Stephen

    Good List.Thanks for posting the same. It will be really useful for administrators like us.

  5. posted by Mohit Mathur on Friday 31 December 2010 AD:
    When Lotus Notes errors hits your database, you can try Stellar Lotus Notes Recovery software which repair corrupt NSF file and recovers all emails, attachments, calendar entries, contacts, to-do, journals, and personal address book templates from lotus notes file.
  6. posted by Nitesh Kumar on Tuesday 08 March 2011 AD:
    Emoticon laugh.gif Emoticon shocked.gif Emoticon rolleyes.gif