It does seem a little sub-optimal.
Have you tried a few different combinations of flags?
without the -v to keep verbosity down
With the -t to change the output backup type (transportable)
Try it through the tcp/ip interface (localhost:c:/path/to/ACC-0007.FDB)

All of these have slightly different execution paths, and if the behaviour
changes, it'll be easier to track down the usage in the code.


Nige.

-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com]On Behalf Of Chau Chee Yang
Sent: Wednesday, 1 November 2006 4:32 PM
To: firebird-support@yahoogroups.com
Subject: [firebird-support] GBAK.EXE consume lot of physical RAM if backup
a big database


Hi,

I backup a firebird database with GBAK.EXE with the following options:

gbak -b -v ACC-0007.FDB c:\temp\a.gbk

The Size of ACC-0007.FDB is about 800M and the a.gbk size is about 500M.

When gbak is running, I open "Windows Task Manager" and notice how the
Physical RAM is use. It happens that the physical RAM keep decrease
while the backup is running. When the backup is going to finish, it
has consume about 500M.

When GBAK.EXE finish running, the RAM is release and back to normal.

Is this the way of how the GBAK.EXE works? It seems like this is a
good design or there are switches in GBAK to turn this behavior off?

I am using Firebird 1.5.3 on Windows XP Professional.

Thank you.

Best Regards,
Chau Chee Yang






[Non-text portions of this message have been removed]