Why does the backup file size change even if database is not in use?

If you run regular backup, you may notice that both database file and backup file size change after each backup, even though there isn't any application using the database. Reason for this is the backup itself. When backup is initiated via Services API or directly with GBAK it starts a snapshot transaction in order to read the data. Each transaction is recorded in header of database file (in transaction inventory), so the database file will change. Additionally, if you run gbak without -g option, it runs the garbage collection that also changes the database.

If you wish to prevent these changes, use gfix to set database to read-only mode like this:

gfix -mode read_only database.fdb

Do you find this FAQ incorrect or incomplete? Please e-mail us what needs to be changed. To ensure quality, each change is checked by our editors (and often tested on live Firebird databases), before it enters the main FAQ database. If you desire so, the changes will be credited to your name. To learn more, visit our add content page.

If you are a commercial tool maker and your tool features a great way to handle the issue written about in this FAQ, please check out our advertisement page.