The first one will always store at least one backup locally while the second one should be removing local backup files right after they are successfully uploaded to The Hub.

From your question, I understand that you’re running Managed Backups. If those seem to complete successfully and yet, there are still backup files stored locally that would mean one of two things:

– either there are also snapshots running (“Snapshot -> Snapshots”:wink: and if so, the only thing that could be done would be to minimize the space it takes by making it keep less backups; that can be set in each of the snapshots configuration (“Snapshot -> Snapshots -> “Edit” for every defined snapshot) in “Local storage limit” section that is visible if snapshot is set to run on schedule (it’s not available if it’s ‘once off” snapshot)

– or the managed backup actually fails – either to be completed or to be uploaded to The Hub.

That said:

– are you running only Managed Backups or both Managed Backups and snapshots?
– did you check if backups are successfully uploaded to The Hub ?

Let me know please. It would also be helpful if you could enable support access to (for the start) one of the affected sites. To do so, go to the “WPMU DEV -> Support -> Support Access” apge in site’s back-end, click on “Grant support access” button there and let me know once it’s done.

I’m a little unsure. I think I’m just using managed backups (not snapshots) and it looks like they’re uploading to the hub fine but there are large files still sitting on the server which I don’t think they should.

I’ve granted support access for forresholidays.org – are you able to take a look and help me work it out. It’s happening on two other sites which are linked to this but completely separate installs but may be let’s start with this?

Thanks for granting access, I had a look at your site and can see that the backups are properly created so they shouldn’t be on your server anymore.
I did notice that there was one backup that was taken 2 weeks ago but was uploaded just yesterday, so it could be that there was some hiccup at that specific time that prevented the communication with your site and the upload failed so the plugin stayed on your server.

Is this the only backup not removed from your server or are there more files left there?

Could you provide us with FTP or cPanel access to this site so we could check further why the backups aren’t getting removed?Note: Don’t leave your login details in this ticket.
Instead, you can send us your details using our contact form https://premium.wpmudev.org/contact/#i-have-a-different-question and the template below:
Don’t change the selected topic in the dropdown, just leave it at “I have a different question”.

Those zip files are leftovers from backups that did not manage to complete due to timeouts caused by system running out of resources. In short, the zip files got too big for the server to handle. This seems to be not consistent, so it can be related to site traffic at the time, specific processes running in the same time with backup, other cron jobs, if it is on shared hosting other shared sites’ load etc.

The ones in the snapshots/_backup folder are from several attempts to complete the same backup and each time it would time out. The zip in the snapshots folder is the one left probably when the zip was created from the ones in the _backup folder but it either timed out before the zip was completed or during upload.

In any case this is related to resources, as handling zip files of 500mb is resource intensive. You can delete those files so they don’t take up your space and with your permission I could run a few tests to see if there is anything we can do in order to reduce this high load, by using some defines in Snapshot. It’s a long shot (as it’s not consistent) and we would need to do multiple tests with those in order to see if those would indeed help in your case, that’s why I would need your confirmation first.

You can try adding those on your own and keep an eye on the zip files there.

Something else that might help reduce resource demand, could be to exclude the plugins and theme’s folders, especially if you have a big number of plugins. Those can be considered as static content, meaning that those can be reinstalled, and focus backups on db and media files.

I’ve messaged Panos again and made sure that he’s got your message. He’ll get back to you as soon as possible so please keep an eye on this ticket for further updates. I apologize for keeping you waiting!

I see that latest backups are not completed so it’s definitely related to server resources. I have excluded the plugins and themes from the backups also added the defines mentioned above in your wp-config.php file.

I couldn’t wait for a scheduled backup to start so I ran a new managed backup and it completed successfully. This should also help the daily scheduled backups too.

You can keep an eye in your backups page in admin in the following days:
site.org/wp-admin/admin.php?page=snapshot_pro_managed_backups
where it should list your daily backups.

There are still some big ZIP files in that folder that are taking up server space. That was the original issue – backups were happening (to WPMUDEV servers) but weren’t being removed from the server so I was regularly hitting my quota.

Those are the ones that failed to complete and that’s why they were not removed. You can delete the ones that are there manually from cpanel (it will take much longer via ftp). So my next concern was to avoid repeating this issue again and keep adding new leftovers when future backups fail to complete.

With thosee changes mentioned above I believe that they won’t be failing so there shouldn’t be new huge zips added in your uploads folder.

Make sure you place those before this line/* That's all, stop editing! Happy blogging. */

Next you can try excluding plugins and themes from backups as done in the current site. To do so, you can add the paths to those folders in Snapshot settings under the Global File Exclusions section here : yoursite.com/wp-admin/admin.php?page=snapshot_pro_settings

In order to get the full paths for those folder you can go to Tools > Site Health > Info. Those should be in the Directories and Sizes accordion:
yoursite.com/wp-admin/site-health.php?tab=debug

I just tried now and the backup completed. As this is a backup written in php, it does add a lot of overhead on the server on it’s own (that’s why we’re re-writing it so it supports incremental backups ), but there are other facts that affect the backup too. For instance other processes that might be running at the same time on server, number of visitors, if it is on a shared environment number of visitors on other sites that share resources and so on.

Something else that might be happening is that when running a managed backup manually, this is done via ajax. So if the pc/laptop you are using goes idle, then the process will fail. When testing that make sure you set your pc/laptop to not “sleep” for a few hours, until this finishes.

For the other sites you mentioned could you create a separate task so we can give them a look too? Or you can use our chat support and provide admin/ftp access there directly.

How do you rate me?

Thank you for rating your experience!

We’re thrilled to hear you had a great experience with .
Would you like to leave a comment about your experience?
Thanks for voting on your experience with , we’d love to
get some feedback please.
Ohh no! We’re really sorry to hear you didn’t have a pleasant experience with
, we’re always looking at how we can improve and would
appreciate you provide some further feedback here please.
Type your feedback here

it's great that you had a positive one. Based on your experience in this ticket would you
please be kind enough to rate us externally on: