Has anyone encountered the problem that databases are all of sudden gone/deleted ?We’re running clusters of 2 servers.
It happened w/ Domino version 6.5.x and 7.0.3
It happened within different clusters.
It happend on different db’s (custom db’s as well as mail files).
Can this problem be related to backup software (CA-Brightstore) ?
Can this problem be related to AV soft (Symantec MS4Domino) ?
Can this problem be related to running out of free disk space?
Is it possible to monitor (send alerts) on db deletion ?
Tx & rgds.
Subject: Databases suddenly deleted
As a rule of thumb nothing just gets deleted. Normally there is something or someone that is guilty of the fact.
If Domino is at fault you should check the adminp process and see if the database was deleted via that. This will also state who asked for it to be deleted.
The cluster might be of issue, more importantly human error relating to the files being in the cluster. Marking the DB as pending delete will make Domino automaitcally delete the DB once all pending data is written to the DB.
Other than this Third parties can remove DB (files) from the OS but that would have to be programmed to do som but check these logs for the infomration you would need.
I hope this helps.
Subject: Databases suddenly deleted
To answer the last question, yes, you can monitor for deletions. Create an Event Handler for events that contain the event:
“Database deleted by ”
You can configure the appropriate form of notification (e.g. email).
Subject: Databases suddenly deleted : solution
We were running compact task with option -c -L -i and HP Brightstore backup soft at the same time (large amount of data to backup & compact) which renamed the db as explained in the Technote below.Changing the compac option to -B solved the problem.
Domino Databases Seem to Disappear After Compact -c Has Run
Technote (FAQ)
Problem
After running the Compact task with the -c switch, existing databases seem to have disappeared.
The following error may also appear in the LOG.NSF:
“Compaction failed: Unable to rename c:\directory\dbname.tmp back to c:\directory\dbname.nsf: Database is currently in use by you or another user - You must rename it yourself.”
Solution
What has actually happened is a third-party product had a hook into the data during the Compact process. When Compact tried to rename the TMP file back to “DBNAME.NSF”, it was unable to.
The Solution is to locate the “DBNAME.TMP” and manually rename it back to “DBNAME.NSF”.
It would also be advisable to stop any third-party process while running Compact with the –c switch.