Caspar

If I read correctly, did this comment solve the issue for you?

@civalp Thank you for posting your solution.
freica97 Thanks for confirming.

Hi Stephan,

thanks for posting. Would you post am anonymized log file of that backup job for us, i.e. at https://pastebin.com/?

Thanks,
Caspar

Hi everyone,

the issue here doesn’t seem to be the errors, but the preceding warning. Whenever you see a warning like WARNING: Job restart due to inactivity for more than 5 minutes., it has to do with a timeout during archive creation. The timeout is most likely to be caused by limitations on script execution set by the hosting company. Those can largely vary from host to host, so it is almost impossible to define a preset in the plugin that works for everyone.

Therefore since BackWPup 3.0.6 there’s an option labeled Restart on archive creation in BackWPup->Settings->Jobs. Here you can manually set a number of x Megabytes BackWPup will add to an archive and then pause before adding another x MBs to the same archive. That way we try to avoid for the backup process to be canceled server-side because of a timeout for script execution.

What you can do is:

• Test out (trial/error) the number of MB that works for your server.
• If that doesn’t work for you, split up a backup job into smaller backups (i.e. an extra job for /uploads).

Splitting up large backup jobs into smaller ones might be a good idea anyway if your site contains a lot of uploaded files.

It should say:

Backup to Folder
Backup sent by e-mail
Backup to FTP
Backup to Dropbox
Backup to an S3 Service
Backup to Microsoft Azure (Blob)
Backup to Rackspace Cloud Files
Backup to SugarSync

If it doesn’t, it’s most likely due to missing server requirements.

Hi eitanc,

the missing method was a down-right bug. It has been fixed in our development branch already and will be gone with the next plugin update.

Thanks,
Caspar

I guess it goes on our issues list then. Sorry, can’t solve it for you right now.

Forgot: there is an option in Settings->Jobs named “Restart on archive creation”. Playing with MB numbers here has solved a similar issue before for one of our Pro users. Maybe start with 100 and trial/error from there.

@gonzalez74 Same suggestions as above.

@ikaring We’re working on a couple of issues all related to uploading to Dropbox. The strict warning in your log file is related to a bug in the sdk we’re waiting for to be fixed. The timeout obviously happens before that, though.

I have tested archive of about 48MB, and it was successful, only once though. Also, excluding uploads folder went fine. (archive size was 1.5mb)

For now, I’d say smaller jobs are the way to go then as the timeout seems to be related to file/folder sizes. Is there anything else possibly working on your server to limit script execution time? Are you in a shared environment or on your own machine? Some hosts don’t touch max script execution time in PHP, but implement other limitations. If your on a shared server, maybe your web host can shed a bit of light on this.

I’m marking the topic as resolved since the issue doesn’t seem inhere in the plugin and splitting backup jobs up into chunks does provide a way—albeit not the most elegant—for you to create complete updates.

No idea. We can’t reproduce the error, and to my knowledge there is no one else has had the same issue. I’m honestly sorry, but it seems I won’t be able to solve this one here.

Nope, not right now.

Hi budestrings,

thanks for your feedback. The update obviously has brought some issues for a couple of users which we try to solve. Are these server side or plugin issues? From our perspective they are mostly related to server-side settings as for the majority of our users BackWPup seems to run very smooth.

I’m marking the topic as resolved since its originator peter hasn’t come back here and you are able to backup your site by now. However, the issues with archive creation and uploading backup archives to cloud services are subject to track and work on for us.

Thanks again,
Caspar

@nykess As Erle says, “dump” in this case means to store those table in the backup file. I can see the term maybe should be banned from our UI since it can be misleading. ??

@erle Thanks!

That’s PHP 5.2.4 then? As the message says 5.2.6 is required for BackWPup to run properly. Which doesn’t mean, of course, everything fails at a lower PHP version, but weird things can happen. No idea why the message hasn’t showed up earlier, but it is correct.

@fngeditor

If any of the developers on this thread would like it, I can start it, and just give it the time to fully fail. After that, I can upload and post a link to the log file.

Please do!
Meanwhile, as clear as I understand there’s an issue and I’m hoping we’ll be able to solve it, the plugin is not broken in and out of itself. It works like a charm on what has to be assumed a couple of tens of thousands sites out there (given the 0.5mio downloads it has altogether).
Dito @edwinkort.

@rogerwheatley As I suggested here, a support forum sure is the wrong place to start a conspiracy theory. Let’s work on issues and treat each other fair here.