Greg Kay wrote:

> Hi,
>
> We're running Firebird Classic 1.5.3 and have a 25 Gb database with
> about a million transactions per day. Occasionally we have the corrupt
> index problem you mentioned.

That's interesting. Generally, gbak doesn't use indexes since it does
a complete scan of each table. What indexes are you finding problems
with? When it backs up indexes, it backs up only the definition, not
the contents. What error do you see?

>
> Just out of interest, is this problem likely to occur in Firbird 2.0?
>

There have been a lot of changes to the indexing code, and the problem
(whatever it is) may have been fixed as a side effect.


Regards,


Ann