Before this falls away to oblivion, I have had several instances where GBAK will
simply stop backing up in the middle of doing it's job. In these instances,
trying again, sometimes a few times gets it to go. I've often thought that maybe
it was due to some resource not being available to something somewhere, but I
can never reproduce it reliably.

Jason

Dave Byrne wrote:

> Thanks Alexandre, Steve and Pavel,
>
> When I used the -g switch, both databases backed up fine.
>
> Thanks again,
>
> Dave
>
>
> -----Original Message-----
> From: firebird-support@yahoogroups.com
> [mailto:firebird-support@yahoogroups.com] On Behalf Of Pavel Menshchikov
> Sent: Friday, September 23, 2005 3:24 PM
> To: Dave Byrne
> Subject: Re: [firebird-support] GBAK hang problem
>
> Hello Dave,
>
> DB> I have a Firebird 1.5.2 database file that is 230 MB and I try to
> back
> DB> it up with the following command:
>
> DB> C:\public\gbaktest>gbak -v -t -b
> DB> c:\public\gbaktest\asset5.fdb -user
> DB> sysdba -pas masterkey c:\public\gbaktest\asset5.fbk
>
> DB> At this point I also notice that the fbserver.exe process starts to
> take
> DB> up 90% of the CPU.
> DB> I CTRL-C gbak but fbserver.exe continues to hog the CPU.
> DB> No one else is using the database. I restarted the firebird service
> DB> prior to running gbak to guarantee a fresh start.
> DB> I have two separate (large) test databases that display this same
> DB> problem. I also have several that work fine.
> DB> Also, just in case this is relevant, the ASSET_EVENT table contains
> DB> several million records.
> DB> Any ideas on what could be going wrong here?
>
> Garbage collecting? Try to disable it with the appropriate
> command-line switch.
>
>