Support

Both local and remote quotas do work. I use them on a daily basis both in production and in testing. Even in development I do use remote quotas (and frozen backups, to avoid remote quotas harvesting what shouldn't be deleted); some dev sites' archives are stored on a separate server, sent over using the Post-Processing Engine feature in Akeeba Backup.

Please read https://www.akeeba.com/documentation/akeeba-backup-joomla/local-and-remote-files.html where I explain how quotas work.

Most commonly, I see people get confused by one or more of the following:

• Quotas apply per backup profile, not globally.
• Quotas apply on complete backups (status OK or Remote). They do not apply on backups which are marked as still running, or having resulted in an error.
• Remote quotas apply only when all of the archive part files have been uploaded to the remote storage. If some / all of the files are still present locally the results are not guaranteed since your backup is neither local nor remote, it's in an undefined state.
• Local and remote quotas are separate. What happens on your server does not necessarily happen on your remote storage and vice versa.
• They operate based on backup records in your database, not files on your disk. If you have deleted a backup record for any reason (restored an older version of the site, manually deleted a backup record, too low obsolete records quota limit, etc) that no longer present record CANNOT participate in quota management, and the respective files will remain.
• Because of the item above, deleting files from your storage does not magically make that backup record ineligible for participation in the quota management; Akeeba Backup won't check for the existence of files before calculating quotas.
• Frozen backup records do not participate in quotas. That's the entire reason of the Frozen flag's existence.
• Whether the latest backup is included when calculating remote quotas or not is an option. Do not assume it's one way or the other; you need to tell Akeeba Backup what is your assumption.

Correct. Upon restoring a backup, you are overwriting the database table #__akeebabackup_stats which holds the information on the backups taken. Therefore, Akeeba Backup no longer knows about the backups taken between the date of the backup and the date of the restoration. These will remain in the remote storage unless you manually remove them. It's easy to spot if you're using the backup date as part of the backup filename (that's the default). When you list the files on the remote storage, these forgotten files will stick out like a sore thumb, as they do not follow the date pattern of the other files.