At 10:57 AM 11/08/2004 +0200, you wrote:

>Hi all
>
>Firebird 1.5.1
>
>Gbak was busy doing its usual thing last night and this morning reported
>that the backup had completed. No suprise there.
>I wanted to start the restore procedure but couldnt find the backup file.
>Turns outs the backup drive was getting a bit full, so there wasnt enough
>space for the new backup file.
>
>Does gbak seriously not have the capablity to check such a simple thing? Or
>am I missing something?
>I know its good to always check drive space before you do things, but if it
>is a gbak limitation this puts a potential dent in automated procedures.

Hmmm, gbak has no way of knowing beforehand what the volume of data will
be. How would you suggest it could be made possible? And, if it could,
how could gbak tell whether all of the disk space available at the
beginning would still be there at the end? The same applies to any data
duplication operation, be it database backups, replication, system backups,
whatever. The operation will blow up if there's not enough space.

The only way YOU can anticipate the conditions and protected your automated
procedures is to monitor the sizes of database files and backup files over
time and to treat disk capacity as something you have to make provision
for, not entrust to pot luck.

/heLen