Plugin Contributor
bcrodua
(@bcrodua)
Hi Alex,
The log clearly shows a Google Drive quota error (403 – storage exceeded).
Even if space appears available, Google can still block scheduled uploads if the account is near its limit or if trashed files are still counting toward storage.
Please empty the Drive trash completely and free up some additional space, then try again. You can also lower the split archive size to 50MB.
Let us know how it goes.
Best Wishes,
Bryle
You can see: available=6570.4 MB and uploaded file size is only 400 MB. Drive trash is empty. Full backup size is now less than 10GB. Disk quota is 15 GB.
Until v. 1.26.1 everything worked well. I had 15 GB on google drive and about 14 GB backup size.
It seems as if trashed files from previous backup are still counting toward storage. It began a month ago.
Can I send you backup log?
I see in log, for example, that previous backup files are deleted from google drive only after new backup was created and uploaded and gained disk quota limit. Also I see some warnings there.
Plugin Contributor
bcrodua
(@bcrodua)
Hi,
Yes, could you please provide a copy of the full backup log from the failed scheduled backup? This will help us see exactly what is happening with the Google Drive quota error.
Paste the contents into Pastebin (or similar), then share the link here.
Best Wishes,
Bryle
you can get it from here: https://infosecportal.ru/wp-content/uploads/2026/03/log.c2ac52452a2f.txt
tell me when you get and I’ll delete the link
-
This reply was modified 1 month, 2 weeks ago by
astahov006.
Plugin Contributor
bcrodua
(@bcrodua)
Hi,
4860.095 (7) Google Drive: Upload exception (UDP_Google_Service_Exception): Error calling PUT https://www.googleapis.com/upload/drive/v2/files?uploadType=resumable&upload_id=AGQBYWwkwguI8lhj9h3XAkOvTu6aPW66-qBfhdIcTIfbg36wbE8P1_lDgyJWD5yIAg3WNw5Pfw1w_nlxHd1PNmhKFFKy8JkM9cnOjq-Ax3QZrKE&session_crd=AHSoBRVcteZfbYV1EucBhMXmiAWgAWNqNbzSu5_bPnAjWsuIs_tAukEzAThlFsJ8RX6GqAMf-P-xCviRw2Y: (403) The user has exceeded their Drive storage quota (line: 110, file: /var/www/fastuser/data/www/infosecportal.ru/wp-content/plugins/updraftplus/includes/Google/Http/REST.php)
I understand the confusion, but the log shows a direct 403 error from Google’s API stating that the Drive storage quota has been exceeded.
Even if some space appears available, Google can still block uploads if the account is very close to its limit or if files in Trash are still counting toward storage. Since UpdraftPlus uploads the new backup before deleting old ones, the upload must succeed before retention cleanup can occur. If Google blocks the upload, deletion will not run.
Please permanently empty the Google Drive Trash, free up additional space (not just a few MB), wait a few minutes for the quota to refresh, and then run a manual backup again.
Let us know the result.
Best Wishes,
Bryle
Hi!
I’ve no problems with manual backup because I delete previous backup first and have enough space on google drive.
If UpdraftPlus uploads the new backup before deleting old one that means that I need more than double space on google drive scheduled backup to be successful. That’s wrong strategy. In previous versions of UpdraftPlus it was not so. I have 15 GB on google drive and scheduled backups of 14,5 GB in size ran well.
In v. 1.26.1 I need now no less than 30 GB on google drive to run scheduled backups of 14,5 GB in size. Looks absurd doesn’t it?
Regards, Alex
-
This reply was modified 1 month, 2 weeks ago by astahov006.
Plugin Contributor
bcrodua
(@bcrodua)
Hi Alex,
Thanks for the explanation. UpdraftPlus uploads the new backup before deleting the previous one to ensure there is always at least one complete backup available. This is intentional and prevents situations where the old backup is removed but the new one fails, leaving you with no usable backup.
Because of this safety mechanism, sufficient storage space must be available for the new backup to complete before the old one is cleaned up.
Best Wishes,
Bryle
Hi Bryle
The correct sequence of actions should be this: First, a full local backup is made, then the previous backup is deleted from Google Drive, then the local backup is uploaded to Google Drive, then the local backup is deleted. In this case, I am guaranteed to have either one full remote backup or one local backup.
And UpdraftPlus has now done it in such a way that as a result, I don’t have a single backup, since UpdraftPlus deleted the previous backup from Google Drive, and couldn’t completely upload the new local one to Google Drive. If I have enough space on Google Drive for several backups, then I will indicate so in the settings.
That’s why I’m trying to explain to you that this is a mistake. You don’t have to do that. And this error appeared only in the latest version of your plugin.
Regards, Alex
-
This reply was modified 1 month, 2 weeks ago by astahov006.
Plugin Contributor
bcrodua
(@bcrodua)
Hi Alex,
In old version of UpdraftPlus it used to created the entire backup locally first and then uploaded it to remote storage. However, this caused problems for many users with limited local disk space, so the process was changed based on frequent user requests.
Now, UpdraftPlus creates each archive part locally and immediately sends it to the remote storage, rather than building the entire backup first. This helps avoid running out of local storage during large backups.
If the remote storage runs out of space during upload (for example with Google Drive quotas), the backup can fail before the upload completes.
Ensuring enough available space on the remote storage for the backup size is therefore important for scheduled backups to complete successfully.
Thanks for sharing your feedback — we appreciate it.
Best Wishes,
Bryle
Hi Bryle!
Thank you for the detailed explanation.
It’s strange not to have enough space for at least one full local backup. To restore data, it is preferable to have a full local backup first, otherwise difficulties may arise. The recovery process in this case will be more error prone.
Perhaps you could give the user the choice of doing a full local backup as before, or doing and downloading it in parts. Or, just before starting a backup, you can simply estimate the space in local and remote storage and choose an optimal action algorithm depending on this.
I can now rollback to the previous version of UpdraftPlus to solve this problem. But I know that in previous version Google Drive chunked uploads didn’t resume from where it left off but started from the beginning resulting in file duplicates. Should I choose an even earlier version than 1.25.8 to avoid this problem?
Regards, Alex
Hi,
I would not recommend that you use an older version of the plugin. You would have to roll back quite a long way.
Uploading the backup and deleting the files immediately after they have uploaded makes backups a lot more likely to succeed for users with limited quota. We did this in response to a huge amount of customer demand and we are unlikely to go back to doing the whole backup before loading.
You can download the backup in the backup/restore tab in parts
When you say duplicates, can you take a screenshot?
Hi
You’ve solved the problem of users who don’t have enough local backup space, but you’ve also created a problem for others. I have 15GB of free space on Google drive and а month ago I still had no problems running scheduled backups of 14GB in size there. Now I can no more run scheduled backups of even 9GB in size. I don’t think this is the right decision. Most likely, many users like me will now ask you to fix this. We often face a lack of local or remote storage space and backup algorithm must take it into account.
I read about the problem of duplicates in your changelog of v. 1.26.1 – 19/Jan/2026. And I remember that I met that problem on some sites earlier but I didn’t save the screenshot.
Regards, Alex
Hi
I installed v. 1.26.2, ran scheduled backup and it completed successfully.
I see in log that UpdraftPlus made zip files and uploaded them one by one on google drive till the disk qouta was exeeded. Then it continued to make local copies and when full backup was made locally UpdraftPlus deleted previous backup from google drive and then uploaded the remaining zip files.
This is exactly the behavior I need. Thanks.
Have you managed to correct this algorithm in v. 1.26.2 or what it was?
Regards, Alex
