|Subject||Re: GBAK.EXE consume lot of physical RAM if backup a big database|
|Author||Chau Chee Yang|
> It does seem a little sub-optimal.I have tried the following combination and it doesn't work:
> 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)
1. gbak -b acc-0007.fdb c:\temp\a.gbk
2. gbak -b -t acc-0007.fdb c:\temp\a.gbk
3. gbak -b localhost:C:\db\acc-0007.fdb c:\temp\a.gbk
4. gbak -b -t localhost:C:\db\acc-0007.fdb c:\temp\a.gbk
The RAM is consumed as usual.