Support

Are you using any kind of post-processing, e.g. send to S3, send to email or anything in the like? If so, can you try disabling it?

Do you have setup anything which might be clearing your cache directory, e.g. enabling this feature on the "System - Admin Tools" plugin? If you did, try unsetting this option. Does that solve the problem?

It's not necessary to add these directories as exceptions to the .htaccess Maker. Those exceptions are only required for web access to the files in them (aklazy plugin does no such thing). Can you verify that all of the scheduling settings in the "System - Admin Tools" plugin are set to No (no scheduling)? If that is so, it's still possible that since your backups are moved to an off-site location that the lazy plugin picks that up and thinks that your backup is out of date. That's a limitation of the plugin, as it wasn't conceived for that kind of backups to be perfectly honest; it's supposed to be the last ditch attempt at scheduling your backups.

I consider native CRON jobs with backup.php, altbackup.php and wget with the front-end backup feature (as detailed in our documentation) to be far better approaches. In fact, I am considering ditching the aklazy plugin altogether in the next minor release of Akeeba Backup.

No problem! You're welcome :)