Fred, just a couple of comments -

> We have an "automated" backup and restore for our sites. Here's what we do
> (Server = NT4.0 or W2000), via .cmd files and the windows scehduler (AT
> command):
> - make sure there are no connections to the database by stopping IB, copy

a

> service file that has no gds entry (to stop anyone from logging into IB
> until we're finished), and restart IB

Wouldn't a rename be just as good, seems that doing a services file seems a
little sledge hammery (you need a file with the one line ommited).

> - Backup the database using gbak to a backup directory and check for

errors

> - If errors, log the event to a log file, stop IB, copy the old services
> file back in place, restart IB and quit

Surely if the backup fails, you must suspect the source db, do you really
want users continuing to use the db.

> - If no errors, stop IB, then, using the command "MOVE", move the active
> database directory to a "save" directory.