Support

Akeeba Backup for Joomla!

#30526 Strange Behaviour of Remote Backup

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
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

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by on Wednesday, 09 January 2019 17:17 CST

spot86
Hi dear,

I've setted Akeeba for automatic backup and archiviation ind Dropbox.

I noted that Akeeba starts to (form 11th of November) to do this:

- Load a file in Dropbox, about 2 GB, .zip format
- Load a file in local server, about 2 GB, .z01 format

Prior to 11th November, backup was stored completely on Dropbox, with this difference:

- .zip of about 330 MB
- .z01 of about 2 GB

I can't store backup on local server and want your help to solve this.

Hope you can

Log Folder: https://www.oukside.com/backup-log.zip

nicholas
Akeeba Staff
Manager
Your backups have zero size. Please go to your Configuration page and set the Log Level to "All Information and Debug". Take a new backup. When the backup is done click on View Log. Click on Download Log. Put the downloaded file in a ZIP archive. Attach the ZIP archive to your next reply. This will help me help you.

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!

spot86
Hi Nicholas,

here the last logs: https://www.oukside.com/akeeba-log-oks.zip

nicholas
Akeeba Staff
Manager
According to your log file both parts of the backup archive have been uploaded successfully to Dropbox. One part is 2GB, the other about 380MB. Nothing is left behind on your server.

Most likely the large files you see on your server are leftovers from a previous, failed backup attempt. Try deleting them and then take a new backup. If you see that the uploaded .zip and .z01 file are still left behind go to Configuration, Post-Processing, click Configure and select the option to delete the files after upload.

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!

spot86
Thanks, Nicholas.

The option in configuration (delete file after processing) is yet enabled.

Hence the file I saw, at this point, are failed backup.
What are the common cause of these (failed backup)? Maybe the size of the files?

nicholas
Akeeba Staff
Manager
Considering that larger files did make it through, it's not the size of the file per se. It could be a temporary network error which prevented the file transfer. Or your server might have killed the backup process for any reason. In short, it was a random and temporary problem. It looks that there's nothing you need to do on your end.

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!

spot86
Hi Nicholas
I waited some times and check if the backups were stored in the local folder and...

The problem persists.
I put the last logs in the same file: https://www.oukside.com/akeeba-log-oks.zip

(until 6/12, 'cause I changed from 6/12 the log level deactivating "All information and debug).

Any other input?

nicholas
Akeeba Staff
Manager
According to the log file the file was deleted:
DEBUG   |181202 23:24:02|Deleting already processed file <root>/backup/site-www.oukside.com-20181203-062001.zip


Please note that only the file from the backup currently being taken will be removed. Any older / leftover files will NOT be removed.

If the file mentioned in a "Deleting already processed file" line has not been deleted from your server please contact your host. Akeeba Backup uses PHP's unlink() function to delete files. It's the same function Joomla! itself uses to delete temporary, cache, installation etc files. If this function does not work properly it's something your host should know and fix. We have no further control over the matter.

Finally, I'd like to note that you are the only person who is reporting this issue. If it was really a bug for such a fundamental issue we'd have definitely received reports for it, let alone experienced it ourselves on our own production sites. This tells me that you are either looking at the wrong file (mistakes happen), expect a file from an earlier backup to be removed (it won't; you'd have to do it manually) or something is wrong with your hosting environment. I hope this helps you figure out which of these issues outside our control results in the effects you observed.

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!

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

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!