We execute gbak -b on our customer's databases to test if they are ok or corrupted
Recently we tried to launch gbak -d to create Dump file (on each week) to reduce time needed for this task, Dump only update modified pages once the first Dump is done

But it seems gbak -d doesn't return any error on a corrupted database, the file is created or updated just like it was a valid DB

Is there an option to add with gbak -d which allows to test the validity of the DB ?

Thanks
Yves

It should be noted that the purpose of gbak is not to detect corruption. 
So, if corruption is a concern, you are well advised to use gfix.

On a side note, if you know how your corruption might be occurring, we 
are always interested in knowing the details. Should this be the case, 
please start a new thread. Thanks.

Yves Ganier wrote:
>> {quote:title=quinn wildman wrote:}{quote}
>> No. If you need to verify the database, use gfix -v -f first.
>>
>> Yves Ganier wrote:
>>> Is there an option to add with gbak -d which allows to test the validity of the DB ?
>
> yes we tried this way, but this is far longer than a gbak -b
> Thanks
>

> {quote:title=quinn wildman wrote:}{quote}
> No. If you need to verify the database, use gfix -v -f first.
> 
> Yves Ganier wrote:
> > Is there an option to add with gbak -d which allows to test the validity of the DB ?

yes we tried this way, but this is far longer than a gbak -b
Thanks

No. If you need to verify the database, use gfix -v -f first.

Yves Ganier wrote:
> Is there an option to add with gbak -d which allows to test the validity of the DB ?