Subject | Re: [firebird-support] gbak is taking a very long time to execute |
---|---|
Author | Theodore Zafiropoulos |
Post date | 2011-01-27T23:11:20Z |
Thanks for the response Thomas,
gbak -v -t -g -user SYSDBA -password "masterkey" DBNAME.FDB DBNAME.FBK
when I create a new database using
gbak -c -v -p 8192 -user SYSDBA -password "masterkey" DBNAME.FBK DBNAME2.FDB
there will be no garbage transactions in the newly created DBNAME2.FDB database?
Would you advise to stop the current running backup and restart using the -g option?
Thanks for all your help
Theodore
[Non-text portions of this message have been removed]
> > Can anyone tell me why the backup command is taking so long? Have I reached a FB limitation?Initial backup still running 14hrs later and at same display ...
> If it is the backup which needs that long then it possibly is theSo does that mean that if I omit garbage collection in the backup process by the command,
> garbage collection, which takes place in the source database.
> If you actually will replace the production database with the restored
> database, then use the -g switch in the backup process to omit garbage
> collection in the source database.
gbak -v -t -g -user SYSDBA -password "masterkey" DBNAME.FDB DBNAME.FBK
when I create a new database using
gbak -c -v -p 8192 -user SYSDBA -password "masterkey" DBNAME.FBK DBNAME2.FDB
there will be no garbage transactions in the newly created DBNAME2.FDB database?
Would you advise to stop the current running backup and restart using the -g option?
> Another thing you could try is to use the service manager way to executeThere are no users on the system currently.
> the backup and restore.
>With a sweep interval of 20000, I sweep should have been kicked in and
>if it has, then it couldn't have done the job properly due to active
>connections/transactions.
> gstat -h has the followingYes, it sounds that auto sweep should be disabled in my case.
>
> Flags 0
> Checksum 12345
> Generation 25467545
> Page size 8192
> ODS version 11.1
> Oldest Transaction 3017525
> Oldest active 25467536
> Oldest snapshot 25467536
> Next transaction 25467537
> Bumped transaction 1
> Sequence number 0
> Next attachment ID 5627
> Implementation ID 16
> Shadow count 0
> Page buffers 0
> Next header page 0
> Database dialect 3
> Creation date Jan 5, 2011 19:12:30
> Attributes forced write
> Variable header data:
> Sweep interval: 20000
> *END*
>In this situation, you could set the sweep interval to 0 (disable
>automatic sweep) and run it scheduled every night.
Thanks for all your help
Theodore
[Non-text portions of this message have been removed]