Also note that certain Domino databases are always open by the server (names -- or Domino Directory, and the log is a list of examples of these files), so running any disk utilities that may alter the file structure or attempt an I/O on a file would most likely affect one of these databases.
One other thing to mention is the backup system you are using. Does your backup software support "Open File" backup? Many vendors supply add-ins that enable systems like Domino and the M$ mail servers to stay active while the backup process is running, rather than shutting them down during backup.
If you have recovered the database successfully, check the consistency of the application by running the fixup and compact tasks with appropriate switches. For example:
Load Compact -c -i log.nsfFinally, in the case of this SPECIFIC database, while the log is an important review and diagnostic tool, it does not contain any configuration settings for your Domino server. Therefore, I would be inclined to "archive" this log database -- due to the persistent errors you are describing -- and begin with a new log. Shut down the server, move and/or rename the log file (i.e., put it in an admin folder under data and call it oldlog.nsf) and then restart the server. When the server initializes it will recognize the log does not exist and will create a new one for you.
This was first published in April 2006