> 3. once quite infrequently (perhaps 2 times a year)
> your backup is restored to another name adjacent to real database then the
> real one is renamed to "oldXXX" and the restored original file is rename

to

> "your real dbname.gdb"
> step 3 has to be done while noone is connected - you have to manage this
> process somehow.

This really comes down to the root of the problem.... I am trying to do
this process regularly. You have said to do it infrequently (twice per
year)
I am looking to automate this process as much as possible. You have
described a process very similar to my current approach, just varying the
times.... What can I do to be sure that I can safely rename one file to the
other? Should I be using MoveFile instead of CopyFile? Is this the answer?

Basically, the database could be modified through a client connecting or
through the interbase server dumping its cache, or whatever it does... I
need to be sure this hasn't happened while I'm renaming the files.

Thanks