At 11:26 AM 28-01-02 +0100, you wrote:

>I used gbak for the first time today.
>
>After some head-scratching, this command worked:
>
>gbak -b - user SYSDBA - pas masterkey MYDB.GDB MYDB.BK
>
>1. where can I find written explanation of all gbak options ?

In the OpGuide.pdf, which you can download from the IBPhoenix site.

>2. does the command above reclaim the space taken by deleted records ?

Yes: it reclaims the space on the pages from which the rows were deleted.

>3. is the command above all what is periodically needed for the correct
>working of FB ?

Yes, for regular database hygiene. But, if possible, you should restore once in a while (how often depends on the amount of change your database endures over time). That way you periodically start with a squeaky-clean database. Also, as your database file grows to about 80% of maximum size allowed by the operating system, you will need to plan a restore into multiple files.

to I say "if possible", meaning that huge databases may present logistical problems in being able to accommodate two copies of the full database on a single system. Given that a periodic restore is going to be necessary to avoid overflowing database file size maximums (a source of horrendous corruption), some admin planning needs to go into working out a practicable way to do a restore.

>4. I discovered that gbak -help lists all the avaiable options, along with
>a short explanation for each one.
>
>Alas! The options are so many that they scroll vertically and only the last
>ones can be read.
>
>gbak -help | more
>
>does not work, too.
>
>Is there a way to read the whole help screen, or was the author of gbak
>naive enough not to allow this ?

Not naive so much as limited by having to support command shells on numerous different operating system platforms. It's simple to redirect gbak's text output to a text file and read it there at your leisure.

Helen

All for Open and Open for All
Firebird Open SQL Database · http://firebirdsql.org
_______________________________________________________