Support

Akeeba Backup for WordPress

#42650 Feature Request

Posted in ‘Akeeba Backup for WordPress’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

WordPress version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Wednesday, 21 January 2026 07:51 CST

alex.preyer

Hi,

I hope this is the right place to send a feature request.

I'm using Akeeba to backup and restore over 200 websites for small customers. My choice for Akeeba was because it is the most powerfull and best configurable plugin tool for the job.

Before I ask for a feature, here's a brief description of how I back up:

I do daily full backups of my client sites, keep them for 7 days, and then delete them except for the version of the first day of the month. These monthly backups I'll keep for one year. So I'll be able to have backup in case a site is hacked and we recognize it weeks or months later.

So for each website, I have 19 backups, every time a full backup. My backup storage is cheap, so space is not the issue, but the server load backing up large sites is high.

Now to my question:

Usually most of the data in a Wordpress website are in the /wp-content/uploads and there in the years folders. Due to this storage system Wordrpess uses, data in past year folders are not changed anymore.

To get backups small and fast, it would be great to have a complete backup and then, for the next backups, exclude all year folders in the upload folder except the latest year.

Ok, I could do this with the directory exclusion, but then I have to change it every year for every site. I also took a look at the incremental feature, but I remember that I read somewhere that this is not a good idea to use it as standard.

Maybe especially for the Wordpress Version of Akeeba it could be a nice feature to have an option (checkbox) to automaticly exclude the past years folders in uploads.

Best 

Alex

 

nicholas
Akeeba Staff
Manager

What you are asking is hyper-specific and would not make for a good feature in a mass-distributed plugin. I am mostly concerned about the ways this can be misunderstood. Too many people would understand this as "exclude any file in my wp-content/uploads directory which was created or updated more than a year ago", or even "exclude last year's uploads and include this year's uploads even though I used a custom media management plugin which uploads directly to a CDN your plugin has no reasonable way of knowing or accessing", or something even more far-fetched which has nothing to do with the original intention of such a feature and everything to do with the way they manage their own site.

That said, you can still do what you want to do using existing features. Granted, it's not obvious, but that's why I am here :) You'll need two backup profiles:

  • Daily full backup excluding the older years in wp-content/uploads using directory exclusion.
  • Yearly files-only backup of just wp-content/uploads (optional but strongly recommended if you value your sanity).

In this case you can add directory exclusion filters every year using WP-CLI. Since what you need to do and when you need to do it is perfectly predictable, you can create a CRON job running in the evening of January 1st every year. Assuming your site's root is /home/example/public_html, your main backup profile is #1, and WP-CLI is installed on your host as wp, you need the following CRON command line:

wp akeeba filter exclude "wp-content/uploads/$(date --date='1 year ago' +%Y)" --profile=1 --root='[SITEROOT]' --type=directories --path=/home/example/public_html

If you were to run this today, it would add a filter to exclude the wp-content/uploads/2025.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

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!