Fabricio Araujo wrote:

>
> But in terms of reliability is not a thing, at all. Some one have
> ideas to make GBAK backups' have 100% "restorability"?
>

First, there's the new backup in V2, which will happily restore a
logically or physically corrupt database. That's probably the answer
most people will use. For gbak, we could set up a mode where the last
stage of the backup is a full restore to a temporary file that would be
deleted when the "backup" finishes. A better solution, which is being
implemented in steps, is to provide switches that disable checks on
logical consistency - don't build indexes, don't perform constraint
checks, ignore primary and foreign key constraints etc. Whenever we add
a new check for logical consistency we need to add the ability for gbak
to turn it off.

Regards,


Ann