Errors during backup of large site to Backblaze

[udadminKeymaster]

Hi James,

You will need to clear enough space for the backup to be created (see: https://updraftplus.com/faqs/how-much-free-disk-space-do-i-need-to-create-a-backup/). UD has nothing in it to automatically delete old backups to make way for new ones (it is intentionally conservative, and won’t delete an existing actual/usable backup to make way for a possible/in-progress one). PHP also has no reliuable way to know if web hosting account space runs out (there’s no standard API for this), so UD can’t know “ah, zip writing is failing because the account is full”. So, you will want to manually delete the old backup (e.g. using the ‘Existing Backups’ pane in UD), and create a new one.

David

[Jason DearParticipant]

I reduced the zip file split size to 100Mb as recommended in that FAQ document. I’m also deleting the unfinished existing backups using the Existing Backups pane, then I’ll try a backup again.

[Jason DearParticipant]

This reply has been marked as private.

[Bryle CroduaModerator]

Hi Jason,

Please could you try to reduce the split archive size further down to 25Mb? Please run a test backup again and let us know if it still fails to complete.

Regards,
Bryle

[Jason DearParticipant]

I’ve done that and started the backup. Given how long it usually takes to complete (around 6 hours) I probably won’t have the final result of that for you until Monday.

[udadminKeymaster]

Hi Jason,

Apologies – I don’t think Bryle had realised that someone else was handling this support request, and looking at the most recent posts he inferred that you were looking for advice on minimising resource usage. It’s not clear to me that further advice was needed. Unfortunately the link you posted in Firefox send has expired – I guess it could only be downloaded once? If you can post it again, I can take a look.

David

[Jason DearParticipant]

This reply has been marked as private.

[udadminKeymaster]

Are you sure you have the version of UpdraftPlus I previously sent? It looks like not – the version number in your log file differs from the version number of the zip I sent, and I’ve just double-checked that by downloading it from the link in this thread. I checked this because the new code doesn’t seem to be in there, judging from the log pattern when it encounters a problem at Backblaze’s end.

[Jason DearParticipant]

I definitely did have, but I think the automatic update mechanism may have overwritten it with the live version, let me see if I can turn that off.

[Jason DearParticipant]

I’ve turned off auto update in the Expert Settings, and replaced the plugin files with the debug version you supplied. Now trying a backup again.

[Jason DearParticipant]

This reply has been marked as private.

[udadminKeymaster]

Hi,

Yes, thank you. This backup does manifest the same problem with Backblaze, followed by successful handling of that problem, resulting in success. This improvement will be in our next release – thank you for your help!

David

[Jason DearParticipant]

That’s great, thank you!

Please let me know once the release version is out so I can turn automatic update back on.

[udadminKeymaster]

Hi Jason,

The best thing to do is manually edit wp-content/plugins/updraftplus/updraftplus.php, and change the Version header at the top so that the given version is 2.16.16.25. That’s the line WP uses when looking for updates. Change it to that, and you can turn the auto-updates back on straight away – it won’t update until our next release.

David

[Jason DearParticipant]

Thanks, I’ve now done that.

[Author]

Posts