At 1/28/2002 05:01 PM, Fred Wilson wrote:

>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
>- 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
>- If no errors, stop IB, then, using the command "MOVE", move the active
>database directory to a "save" directory.
>- Start IB
>- Restore the backup to the active database directory
>- If errors, stop IB, and delete the "restored" database files and "MOVE"
>the save directory back to the active directory, copy the old services file
>back to the original,restart IB, log the event, and quit
>- If no errors, log the event, stop IB, copy the original services file back
>into place, restart IB and we're finished

Fred,

Would you be willing to share a sample script? I have my own, but they
are not nearly as involved as yours. In particular, I'm wondering how you
handle stopping the IB service (assuming NET STOP) if there are users
connected, and how you are checking for errors from gbak.


tia,

Bob M..