BackWPup: Job restarted, bcause inactivity!

@daniel

Any idea when version 3 will be coming out?
Any updates on this issue?
I saw on this post that if you compress with .gz it works

We hope next week.

I’m pretty sure there must be a host-related part to this problem.

I’ve got a VPS where BackWPup can successfully run 600MB backups with 5300 files, but I’ve just installed it on a client’s server and it’s freezing 3/4 of the way through a 180MB 4300-file backup. I THINK they’re hosted on a GoDaddy shared server.

Switching to .gz, or the PHP ZIP option don’t help.

For now, I’ve split their 2012 upload directory out into its own backup job (I figure I don’t need to run *that* very frequently!) and everything’s OK, but I look forward to trying out the new release.

I am new to this plugin, and having the same problem. Though I can add a little bit to the info here. My backups on 2 sites have been failing to backup to Dropbox so I did a little more diagnosis this morning.

1. Backing up just the database worked fine. Although my database seems to be only 400kb?
2. adding ‘File Backup’ and only backing up ‘root folder’ gave me a 5mb file that did appear in my dropbox, but BackWPup appeared to think this had timed out 3 times and kept trying to send. I am hosted on a shared server.
3. the plugin also seems to be having trouble with timeouts before the files are compressed. I am trying to modify php.ini to fix this but don’t have answers yet

This gives 2 possibilities
1. There is something in the plugin that generates the error despite successful file transfer. I don’t think this is correct because when trying to do a full backup it does fail
2. Plugin does not get the successful file transfer message and continues to attempt to send. Not sure about this either

I can’t get any logs from Dropbox so I don’t really know what is happening, but I’d really like to get this fixed. Please let me know if any other tests would help.

I’m now fairly convinced that this is an issue related to the limited resources on shared hosting. I can do repeatable, working backups with 11mb of data, but repeatable failures at 20mb.

The plugin sees nothing bad happening but it may be that the host is stopping something from executing because of resource usage. How do we check this out? Which logs would have these details?

servicemax – really odd that you should see failures with datasets that small. Besides my GoDaddy client, I’ve got another client that’s on a “$5/month unlimited everything” shared hosting plan and her backups are running OK with much bigger datasets than that.

If you (or anybody else) wanted to do some debugging work, I think you’re along the right lines for testing.

The output from phpinfo() will show you how high your current memory limit is – there’s a “memory_limit” parameter output in there somewhere.

If you’re on shared hosting I’m not sure if you’ll be able to make changes to a php.ini… maybe it depends on the company. You could always try ini_set(“memory_limit”, “200M”) or something like that.

Try reducing/increasing PHP’s memory limit and see if it affects things. Try logging the return values from memory_get_peak_usage(true) to see how close the script’s getting to the limit.

If you’ve got access to your server’s error logs, you should see a “PHP Fatal error: Allowed memory size of xxxxxxx bytes exhausted” in the logs somewhere if you’re hitting the limit.

thanks for your helpful post Jon Jennings. I do have some control over php.ini so I increased the memory to 256mb which was the max, and increased the timeout values to 120s which is also max allowed.

For this backup we had selected just the posts from the last few years, 149 files totalling 19.82mb. The compression stage went very quickly, but it seems to hang on ‘uploading to Dropbox’

have asked the host if they can help

I am hoping that an update will fix this issue.

Today I tried to back up to
Sugarsync> same problem
Google Storage> documentation non existent/ couldn’t get auth
FTP server> FTP server would not load properly/ my problem!

I have given up. Hosting company has given up too, saying ‘we do not support third party products’ but they did try.

Such a pity, this plugin has so much promise. Google Drive compatibility and proper documentation and support could make this into a worthwhile purchase! Hint, hint

@jon Jennings: the memory_get_peak_usage(true) will done in the logfile. the results in the hint on the timestamp.

@servicemax: We hope we can release the ne Version this week. Google Drive will come with a later Version. Dokumantation is done in German and will translated in the next time. With the New VErsion u can buy a Pro version with premium support, but it will not resolve all problems on cheap Hoster or Hoster limitations.
The new Version has many improvments that the Jobs can work better.

follow up- the host has now admitted that it is their setup causing the failure. I apologise if I seemed to be getting cranky about this. Very frustrating for all concerned. looking forward to seeing the new version, but it looks like I may still not be able to use it. Sigh.