R. S. Patil wrote:

> Thanks Dan,
> > First off, I would suggest that you never, ever, restore on top of an
> existing database. Create a copy, make sure the copy is good, and
> then you
> can rename the files as needed if you wish to run using the new clean
> copy.
> >
> > Disks are so cheap now there is little reason why, especially for a
> "vital
> banking application", that the client shouldn't be able to purchase an
> additional hard drive and dedicate that drive to database files, thus
> avoiding the problem of running out of space due to other happenings
> on the
> server.
> >
> > The one and only time in the past year since I started using
> Firebird that
> I have corrupted a Firebird database was when the disk ran out of space.
> This was not during a backup, but during normal operation.
> >
> > HTH,
>
> But is there any way to detect whether .gbk is file is properly created ?
>
> Best Regards
>
> R. S. Patil

Do a restore in a other Location.
As I recall this is always the best test for any type of backup.

Uwe