> The problem isn't exactly a corrupt backup, but a database with
> undetected logical errors in the data or metadata. Having the backup
> check the validity of the whole database would significantly
> increase the backup time, but it is possible.

Is there a switch available for that? Or can GFIX be used for that?

> At the moment, for example, gbak doesn't pay any attention to data
> constraints like unique and not null. It could recognize and test
> them ... at a cost. But the kind of problem you're describing could
> be caught by making and restoring a metadata backup - much cheaper
> than restoring 100G of data.

However, for detecting logical errors in the data tables, you need to
do a complete restore. Having a switch for GBAK or GFIX that does that
would help with large databases when run in the night or so.

Regards

Stefan