""Henner Kollmann"" <Henner.Kollmann@...> wrote in message
news:000b01c1cb2c$7d8ebab0$1e5562c1@......

> Sorry,
> I use FB on Win2K:
> Startet gbak with -v but there is no output. Gbak do not use any CPU
> resources, it hangs.

The first step is that you compare the metadata for your original db and for
the restored db (just before the second backup fails). There are tools to
compare metadata if I remember well, listed at my site (but thanks to the
DNS's, cvalde.com will appear as gone for one or two days).
Failing that, be patient and run these commands in the two dbs:

select * from rdb$relations
where rdb$relation_name = 'F';

select * from rdb$relation_fields
where rdb$relation_name = 'F'
order by rdb$field_name;

Replace 'F' by your table's name. You should compare the information in your
original db v/s the db that can't be backed up again. The only entry that
can change IMHO is rdb$field_id in rdb$relation_fields, because gbak
reorders fields but preserves the logical ordering (the one you see with a
select *).

C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing