On Fri, 18 Apr 2014 08:18:02 +1200, Helen Borrie <helebor@...>
wrote:

> In any case, the RESERVE setting has no relevance to the problem

described

> by the OP. "Disappearing database" is an unknown phenomenon. The only

way

> that Firebird can delete a database is by a client connecting to it and
> issuing a DROP DATABASE command. A server admin could delete the file

or

> run a script that connects to the database as a client and performs DROP
> DATABASE.
>
> I think the OP has to go back to the admins of those two servers and do
> some forensics. For protective measures, remove shares from folders

that

> contain databases, review any scripts that might be running on boot-up

and

> limit file system access to those who know what they are doing.

I believe there are actually several options assuming the problem occurred
after a full reboot of the system:
* using the .gdb extension and having file system protection and/or volume
shadowing enabled (although my memories are vague on this, and I am not
sure this applies to current Windows versions)
* having the system in a kiosk mode where a reboot restores an image of
the last know 'good' config of the system (but this is something that
usually requires very explicit configuration)

Mark