Support

Akeeba Backup for WordPress

#42190 How to change status 'Obsolete' to 'Remote'

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
6.8.2
PHP version
8.3.23
Akeeba Backup version
9.0.5

Latest post by nicholas on Tuesday, 19 August 2025 11:40 CDT

LukeDouglas

The backup was completed but the file was not moved to the remote Dropbox location.  So I FTP the files directly and deleted them from the wp-content/backups folder.  The status shows as 'Obsolete'.  How can I change this status to 'Remote'?

FYI, it's rare but I have had a similar situation happen when there was an issue between Cloudflare and the website.

nicholas
Akeeba Staff
Manager

You can't, since you moved those files manually. Akeeba Backup has no reference as to where these files ended up being located.

Instead of what you did, you should've gone to the Manage Backups page and use the Transfer Archive button next to the backup record to retry the upload. If that succeeds, the backup record will be uploaded correctly.

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!

LukeDouglas

Website / Cloudflare caused the transfer to fail which is why I FTP download directly into the Dropbox location. The backup worked fine. 

I know this is a rare issue but it would be nice to have the option to change the status from "Obsolete" to "Remote" when you have manually transferred the file.

 

nicholas
Akeeba Staff
Manager

CloudFlare has nothing to do with Akeeba Backup. At all.

As I explained, you cannot change Obsolete to Remote. The difference between Obsolete and Remote is that in the latter case Akeeba Backup has recorded HOW and WHERE it has transferred the backup archive. This is not something you can or should do manually. You are supposed to use Transfer Archive feature, as I explained. 

The Transfer Archive feature exists for a reason. Temporary network issues DO happen. Neither you, nor me, have any control on your server, your host, their upstream provider, the Internet infrastructure between them and the remote file service, or the file service. A network or other issue anywhere between all those things neither of us controls will cause the upload to fail. 999 times out of 1000 coming back a few hours later and using the Transfer Archive feature will work because that temporary issue has been resolved. Using this feature will also correctly update the backup record so that once you remove the locally stored files it will be marked as Remote instead of Obsolete.

You didn't ask before doing something inadvisable. What's done is done. It's not a big deal anyway. Now you know what to do next time, and why.

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!