--- In firebird-support@yahoogroups.com, "slalom91" <slalom91@...> wrote:

>
> Ok,
>
> So I issued the following command:
>
> gbak "backupfilename" "databasefilename" -r -rep -user SYSDBA -pass
> csib6admin
>
> I end up with the following header.
>
> Database header page information:
> Flags 0
> Checksum 12345
> Generation 31
> Page size 4096
> ODS version 11.0
> Oldest transaction 22
> Oldest active 23
> Oldest snapshot 23
> Next transaction 24
> Bumped transaction 1
> Sequence number 0
> Next attachment ID 0
> Implementation ID 16
> Shadow count 0
> Page buffers 0
> Next header page 0
> Database dialect 1
> Creation date Dec 14, 2006 17:09:04
> Attributes force write, no reserve
>
> Variable header data:
> Sweep interval: 0
> *END*
>
> Still no reserve!! ?????
>

Just studying TFB, and taking a guess here that the no reserve
attribute survives a backup-restore. Perhaps Helen or someone else in
the know can explain when the restore switch is used and when it is
ignored. If it is ignored, then that explains why all the backup tools
behaved that way, because leaving no reserve space is not a good idea
for most databases, so I doubt it would ever be defaulted.

In the interim, try:

gfix -use reserve

Then backup and restore and see how you go.

Adam