Akeeba Backup for Joomla!

#32128 – Any tips for keeping backup sizes small?

Posted in ‘Akeeba Backup for Joomla!’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Friday, 13 December 2019 02:54 CST

Do you have any tips/suggestions for keeping the backup sizes to a minimum?
Other than the obvious remove photos/videos/media...

We're using JPA file fortmat.

Custom Fields
Joomla! version (in x.y.z format) 3.9.12
PHP version (in x.y.z format) 7.2.1
Akeeba Backup version (x.y.z format) 6.6.1
Friday, 13 December 2019 04:55 CST
The size of the backup is determined by the files and database data that you put in it.

Akeeba Backup automatically excludes some files and database data it knows you won't need. On the files front it automatically exclude Joomla's temporary, log and cache folders; your server's logs folder (if it's inside your public root); PHP error logs; PHP core dumps; and Operating System-created folder thumbnail files.

On the database front it will automatically exclude the Joomla sessions table and's file cache which tend to be pretty big.

From that point on it's up to you.

Do you have multiple sites under your public site root? For example sites in subdirectories or even subdomains whose root is a subdirectory of your main site. This cannot be detected automatically and are included by default. If that's the case, exclude them.

Do you have any massive archives (e.g. from manual "backups") that needn't be backed up? Look in your backup log file for "big file" – it will give you an idea of which files are rather big and may warrant exclusion from the backup or even deletion.

Regarding your tables, you may have information you don't want to backup such as Admin Tools security exceptions log (#__admintools_log) or the PHP File Change Scanner's results (#__admintools_filescache, #__admintools_scans, #__admintools_scanalerts). Nothing else in our extensions can be safely excluded.

If you have multiple sites sharing the same database you may want to exclude their tables. Our documentation tells you there are two ways. Either using the Excluded non-core tables in the database tables exclusion page or using the documented regular expression for the same effect (which is better and easier maintainable, in the sense you activate once and never bother with it again).

Third party extensions may keep a cache in the database or the filesystem, or they may have other data you don't necessarily want to keep. Consult their documentation and developers.

From that point onwards your question devolves quickly into the "how long is a piece of string" territory and cannot be replied within any degree of accuracy. All I can say is that if there is any file or database data you are absolutely sure can be skipped from a backup (as in: it won't cause your site to go boom or miss any important stuff when restoring on a new server) then you can of course exclude it with the tools provided in Akeeba Backup.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic

Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Sunday, 12 January 2020 17:17 CST
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!