Database Backup File Is Much Larger Than Database

When creating a backup within Acctivate, users have two options. They can either create a standard backup by just clicking “Start Backup” or they can check the “Overwrite existing sets” box.

If a user chooses not to check this box, the backup process will add a set to the backup file. Sets can be seen as previous backups that are stored within the present backup file. These can be helpful if you want to restore the database from a backup that is a from a date prior to your latest backup.

It is recommended that you have some sets in the system just in case you need to a couple options for restore points. However, as in the case above, having too many sets can be superfluous and lead to a bloated file size in the .bkf file on the server.

If the backup file size is growing too large or significantly larger than the database itself, there are probably an overabundance of sets in the file. In this case, check the “overwrite existing sets” both and then run the backup. This will delete all sets and start the new sets from this point.

It may be a better idea to manage your backup files in addition to the backup sets. As an example, you may choose to append your backup file “Acctivate$Demo.bkf” to be “Acctivate$Demo_January.bkf”, so that all the file contains all the sets from January. You can then create a new backup file in Acctivate which will default to the standard name, in this case it would create a new file named “Acctivate$Demo.bkf”. This will keep your current backup file from being too large and let you move your January backup offsite to a safe location. After an appropriate amount of time you can delete the old backup.

Posted in Database - Last modified on March 7, 2019
Still need help?
Search all content on this site, contact support at 817-870-1311, or create a support ticket.