Support

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.

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.

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.

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.