Support

Akeeba Backup for WordPress

#34793 – Default Profile - Exclude Directories Not Working?

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.
Sunday, 07 March 2021 19:37 CST
edwardcox

Hello again :-)

I have setup a simple Exclude Directory to exclude the Akeeba Backups ( /app/Backups) however as each backup still weighs in at 800+MB I'm assuming it includes the .jpa files in that directory as the size is usually 300-400MB.

I've attached a snapshot of the Exclude Directory setup.

Thank you 

 

Edward.

P.S. Annoying! Trying to upload / attach the screen shot as a .png file - File Type not accepted. Odd.

P.P.S. You don't get an attachment because it wont even accept .pdf! Arrrghh

 

https://nimb.ws/wca1kD

 

Custom Fields

WordPress version (in x.y.z format) 5.6.2
PHP version (in x.y.z format) 7.4
Akeeba Backup version (x.y.z format) 7.5.5.1
 
Monday, 08 March 2021 01:09 CST
nicholas

I just checked, the exclusions do work.

Exclusions do not depend on the profile number. They belong to a profile but whether its ID is 1, 200 or 1,345,672,034 is irrelevant to whether they apply. To make it clear, the profile settings and the filters (including directory exclusions) are columns of the #__ak_profiles table. When a profile is being loaded e.g. as part of a backup they are all loaded simultaneously, as a single database record. While profile settings are encrypted filters are not so there's an even lower barrier to loading them correctly.

You do not need to manually exclude the output directory. As you can see, it's automatically excluded (red icons). All its files and folders are excluded but not the directory itself. This is on purpose. It's so that restoring the backup on a blank site creates your output directory as an empty folder. If it's completely missing, like you did by marking the first exclusion icon, restoring on a blank site will not have an output directory created and further backups will fail miserably.

Attachments in our ticket system work just fine as long as they are under 10MB and their extensions are bmp, csv, doc, gif, ico, jpg, jpeg, odg, odp, ods, odt, pdf, png, ppt, txt, xcf, xls, zip, 7z, rar or json. Note that the extension must be lowercase. The information about the maximum allowed size and the allowed extensions is exactly below the attachment interface. My best guess is that you're on Windows and somehow ended up with an uppercase .PNG extension which is actually not-standard. The only reason it works on Windows is because Windows is case-insensitive.

Regarding your issue, I have some ideas. The top suspicion is always a backup archive being left behind in the root of the site. However, I'd much rather see a log file from your last backup so I can tell you which large files or large directories were included in it.  Please ZIP and attach your last backup's log file for me to be able to do that.



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!



Monday, 08 March 2021 01:19 CST
edwardcox

Hi Nicholas,

Thank you again for the detailed explanation. Very helpful indeed.

Please find attached .zip of most recent log file. (was via CLI).

Edward.

 
Monday, 08 March 2021 02:04 CST
nicholas

Your log file says that the backups folder is, indeed, excluded

INFO |210308 00:00:31|Skipping directory <root>wp-content/plugins/akeebabackupwp/app/backups

You do have a site backup in the root of your site taken on March 6th at 18:00:03 AEDT. You may want to delete it. That's probably what is making your backup archive too big.



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!



Monday, 08 March 2021 02:11 CST
edwardcox

Bingo! .jpa file in root has been removed. It was there for a Kickstart restore but was not cleaned up. Anyway, all good.

Thanks for you time and effort - much appreciated.

Edward

 
Monday, 08 March 2021 03:32 CST
nicholas

You're welcome!

I've found an issue with Kickstart where Clean Up wouldn't remove the backups archive from the site's root. I think that was the case with your site restoration. Now it makes perfect sense. A new release for Kickstart is planned for today, addressing this issue.



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!



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!