Support

Hello,

in the Manage Backups page, is it marked as obsolete?
If so it means that the backup file has been removed per your quota settings. You can read further here

Per the screenshot you sent, the backup archive is no longer stored on your server. Look inside administrator/a_backup where you have told Akeeba Backup to store your files. Does the file (whose name appears in red letters at the bottom of the screenshot) exist inside that folder? Look closely, the first half of the name is your site's domain name and will be common for all backup archives.

If the file is not there it means that it has been deleted. It can be deleted for several reasons:

• You or another administrator deleted it from Akeeba Backup's interface using the Delete Files button.
• You or someone else (or even your host, manually or through an automated script) deleted it from the server, outside of Akeeba Backup.
• You asked Akeeba Backup to upload it to remote storage and checked the option to delete it from your server once the upload is complete (default is checked).
• You asked Akeeba Backup to apply quotas which means that older backup archives will be automatically deleted according to your settings.
• You renamed or moved the administrator/a_backup folder. In this case the path stored in the database, telling Akeeba Backup where the backup archive is stored, is no longer valid. Hence its complaining that the backup is not where it should be: it really isn't where it should be!

The file can not disappear by itself. So, one of my points is correct since you have seen with your own eyes that the backup archive does not exist. Please review all your settings especially since you are the only administrator. It could be something as simple as setting up a quota setting without remembering it or something as complicated as having set up a script which ends up removing the old backups outside of Akeeba Backup.

It is fairly obvious that there is nothing I can help you with any further. The interface is correct in saying that the file does not exist, so no problem there. The reason the file doesn't exist anymore is ultimately one which comes down to user-initiated configuration or a user action. Therefore I will now close this ticket.