joe mccann

Thanks for the reply!

Just to be clear, the bug here is that Updraft is storing infinite local copies of previous backups despite being told to only keep 1. This bug appears to be triggered in this case by the backup process not moving past the remote storage part to get to the stage of scanning old backups for deletion and it didn’t seem like Updraft ever scanned the backups for deletion at any other point.

I’m not suggesting that this backup should have made it over email. That support link doesn’t really seem to apply in this case either since the backup is created and successfully stored locally, which match the text on the support page you’ve linked “If you were sent to this page by a warning from your copy of UpdraftPlus, then this does not mean for sure that your backups are definitely failing because of this problem”. The local backup is not failing, the remote storage part is.

The problem here is that when Updraft isn’t able to send the email it never reaches the next state of then scanning old backups to be removed from the local server. This creates an issue where despite being told to only keep the last good local backup, Updraft has stored 40GB of backups. This is the bug that I’m reporting. The local backups are made successfully they are just never deleted at any point.

For what it is worth I don’t think Updraft should even be trying to send 72MB email attachments, particularly to Google which is probably the mail provider that a majority of people are using and who have published attachment limits that are much lower, but that is a separate issue. This creates this situation where Updraft is going to try to do something it already knows likely won’t work, and then something else isn’t going to work properly as a result (removing old backups).

Hope that helps!