> When I said "crashing" I actually meant that if backing up a database
> with users connected could cause a corruption on it.
>
> So, let me see if I understood. Gbak itself can't cause a corruption,
> right?

Correct.

> The problem must be something else there. In this database, gfix
> wasn't pointing any problem. Then I tried to make a backup. At
> certain point at the beggining of a table gbak seems to freeze (it's
> not actually frozen since CPU stays at 100%). It takes about 45
> minutes until I see some progress on gbak.
>
> Anyway, I don't know what caused this corruption but it's preety
> clear to me that gbak has nothing to do with it.

Where do you see a corruption ? You have a lot of garbage and indices
with low selectivity on this table, i guess.

> Once gbak made the backup and I restored it, the problem was solved.
> It's just strange that gfix wasn't pointing anything.

Use -g switch performing backup.

Regards,
Vlad