We have a previously very stable server which has been running without signficant error for several years now. A few months ago, we started to get errors attempting to read or write to log.nsf. The console shows messages such as:
Cannot write to log file: Database is corrupt – Cannot allocate space
or
lo fixup log.nsf -L
18/11/2006 17:51:08 Unable to fixup database d:\notes\data\log.nsf: Special database object cannot be located
Every time it happens, we have to stop the server, delete/move/rename the corrupt log.nsf, then restart the server. Aside from the hassle, we’re losing important log entries that we need for administration and support. Is there anything we can do to prevent it from happening?
What kind of backup are you running? Using Backup Exec here and I had to remove the mail.box’s and the log.nsf from being backed up and the corruption went away. We even have the Domino Agent for Backup Exec and it still was doing this until I stopped thier backup. Hope this helps.
Thanks, Mike: sounds like a good lead: we are using Backup Exec, so I’ll try your suggestion right away.
It’s curious that it never did this before (we’ve been using BE with the Domino agent for many years now, without issue), but then, these things often are curious…