BackWPUp not deleting old backups in my Dropbox folder

@carlgross
hmm please try to re-create the job, authenticate the job with Dropbox again

OK. I deleted all the existing backup files from my Dropbox, deleted the existing BackWPUp job, and created a new BackWPUp job which runs daily. In the process, I changed the Dropbox destination folder from Kabultec/staging/ to /Kabultec/staging/ Maybe that was the cause of the issue. Let’s give it ~4 days to see if the job properly deletes old backups in the Dropbox folder. I’ll report back here.

Also, when I create a daily backup, on a set schedule, and specify a time–what is the timezone of that time? Is it GMT?

• This reply was modified 4 years, 10 months ago by Carl Gross.

@carlgross

Also, when I create a daily backup, on a set schedule, and specify a time–what is the timezone of that time? Is it GMT?

BackWPUp relies on the WordPress Cron Schedule system, so the time depends on your site Settings ^^

>> BackWPUp relies on the WordPress Cron Schedule system, so the time depends on your site Settings ^^

In my WP settings my timezone is Bangkok, and the BackWPUp cron settings are to run the backup at 3:00 am every day (screenshots). But every day, the backups begin ~6:00 PM Bangkok time. Why is that?

@carlgross
maybe your site did not have much traffics so the pseudo-WordPress Cron not fired correctly.
More detailed information when the cron run, you can install the plugin called: https://www.ads-software.com/plugins/wp-crontrol/
to see if the job is scheduled correctly.

>> maybe your site did not have much traffics so the pseudo-WordPress Cron not fired correctly.

OK understood. The site in-question is indeed my staging site, and I am the only person to access it. So it makes sense that the backup would begin as soon as I login to the staging site, which has been about 6:00 pm lately. So consider that resolved.

It’s been a few days since I made the changes to the BackWPUp job, and the deleting old backups in my Dropbox folder are now automatically deleted, as expected. So I’m glad that’s fixed.

But on my staging site, a backup just failed with this error:

ERROR: Uploaded file size and local file size don't match.

I’ve seen this error frequently with the plugin, but have never understood the reason, or the proper solution. Do you want me to open a new ticket for it?

@carlgross
Sorry about the delayed response, could you help me check in case the backup archive in Dropbox got no issue?
Thanks!

Any update on this? Daily update are being imitated by BackWPUp, as desired/expected. Each completes, with the same error (Uploaded file size and local file size don't match.). But it looks like a backup zip file is still created and uploaded to Dropbox. So what is this error and why is it displaying? Does it mean the backup is corrupted?

Also, the issue wasn’t present for the first few days, but suddenly started (screenshot).

A zip file appears to be created, with approximately the correct file size, and uploaded to Dropbox. But I don’t know if this is corrupted in any way due to the error in the log. I’m still clueless as to why and how this error is appearing in the log.

@carlgross
Can you help me try to download that backup archive then check if the file corrupted?
The warning shows up means the uploaded file size(in bytes) reported from Dropbox server did not exactly match the one created.

In my Dropbox folder, the two most recent zip files are present (as desired/expected).

Usually, while logged in to Dropbox, I am able to open a zip file and browse its contents. But with these two zip files, I cannot (screenshot).

If I try to download each of files, they both download without issue. I can then open each on my local computer without issue.

The zip files contain sensitive info (e.g. wp-config.php), so I don’t want to share it with you. Is that OK? Or would it help if I removed sensitive info, then shared it with you?

>> The warning shows up means the uploaded file size(in bytes) reported from Dropbox server did not exactly match the one created.

Right. I understand it is saying that. But I don’t understand how that can occur. How can the uploaded file size be different from the one created? Does BackWPUp (or Dropbox?) somehow alter the file size aftercreating the zip file, but beforeuploading to Dropbox? If so, why, and how can we resolve that?

Hello. Any update on this issue?

@carlgross

Right. I understand it is saying that. But I don’t understand how that can occur. How can the uploaded file size be different from the one created? Does BackWPUp (or Dropbox?) somehow alter the file size after creating the zip file, but before uploading to Dropbox? If so, why, and how can we resolve that?

maybe Dropbox server returned a missing few bytes :/
hmm so I actually think we can just ignore these warnings.

I personally have encountered this BackWPUp issue many times over the past few years. And I know there are other posts in the forum about it. Is it still such a head scratching issue, with no possible troubleshooting or resolution? Is my only recourse to just hope that the warnings don’t mean anything? Is there anything we can do–aside from carrying out a full restore of each backup–to ensure the backup was actually taken properly? I’d really prefer a backup system which didn’t produce error messages on every backup.

@carlgross

@carlgross
sorry I have no other ideal about this issue since we did not able to reproduce this :/
But maybe you can help us with how to reproduce the issue, I would need the following information from you to help us (hopefully) able to reproduce the issue:
– Your server information (BackWPUp -> Settings -> Info )
– what hosting are you running on?
– What type of Dropbox account do you use?
– In case you change the backup to another Dropbox account, is the issue still happens?
– Are you able to test on another server/hosting?

Thank you so much!