BackWPup not working after upgrade

Klikerko,

Just curious… what is the size of your backup on the sites (that is… when it was working)?

My backup on the test site is 40some meg (not real large since it is primarily a basic WP install for testing).

Just wondering if there is some kind of timing issue.

Most websites are below 60MB, there is only one with lots of images, I believe has around 250MB backup file. All websites had working backup plugin until exact moment when plugin was updated to version 3. On all sites I’m backing up all files and database.

OK, I did little bit more testing few minutes ago and managed to narrow down issue to backing up files in root folder.

First I tested backing up just the database. That worked just fine. Finished in 4 seconds. Then I enabled file backup and started selecting folders to backup from the bottom up. “upload”, “themes”, “plugins” and “content” worked great. I got backup done in 10 seconds. Last I selected “backup root folder” plugin and process got stock at 50% again.

Next I deselected everything and left only “root folder” to backup but excluded all three options “wp-admin”, “cgi-bin” and “wp-includes”. Backup job started, said there is only 1 folder to backup, and got stuck at 50% again.

So it looks like there is something wrong in the process of backing up root folder, at a beginning, because first progress bar is stuck at 50% but second is stuck at 1%.

I hope this helps. Devs let me know if I can help you with anything else.

This is log from few minutes ago. Why he’s trying to make 4GB backup? Checked and there is no large files on that site.

[20-Mar-2013 20:17:17] Database dump done!
[20-Mar-2013 20:17:17] 1. Trying to make a list of folders to back up …
[20-Mar-2013 20:17:17] 1 folders to back up.
[20-Mar-2013 20:17:17] 1. Trying to create backup archive …
[20-Mar-2013 20:17:17] Compression method is PclZip
[20-Mar-2013 20:22:20] WARNING: Job restart due to inactivity for more than 5 minutes.
[20-Mar-2013 20:22:20] 2. Trying to create backup archive …
[20-Mar-2013 20:22:20] Compression method is PclZip
[20-Mar-2013 20:22:21] ERROR: PclZip archive add error: PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature
[20-Mar-2013 20:22:21] Backup archive created.
[20-Mar-2013 20:22:21] Archive size is 4.03 MB.
[20-Mar-2013 20:22:21] 27 Files with 4.23 GB in Archive.
[20-Mar-2013 20:22:21] 4 old logs deleted
[20-Mar-2013 20:22:21] Job done in 304 seconds.

Klikerko – it might be backing up the leftover files from failed backups. Check the backwpup directory in the uploads directory.

Mine fails with 3.0.6 too. On one site I have the same symptoms as alanudi – the job log doesn’t pop up when i run the job manually, and no log file is written.

On another site, the job completes successfully but the backup file doesn’t appear on S3 or Dropbox. The job did restart due to inactivity during the upload though.

@eugk, you were correct. I just found error_log file in the root directory. Size 4.23GB!

Deleted the file and run backup job again with full file and database backup. All finished fine in 14 seconds!

Is it possible that others might have similar issue?

I want to add to this discussion, but the only helpful response at this point is for the development team to be transparent about their latest release. Caspar and Daniel have been replying intermittently to various complaints in different places. We need a comprehensive listing of issues and a method of following them (ala Github).
My observations to add to this forum are from two production sites, on totally different hosts, where the BackWPup failed in different ways as soon as I updated the plugin from 2.17 to 3.06
In the first case it seems to have lost the authentication information for a Dropbox account. Easily remedied (the error log made it clear), but then I was unable to test. Like others, the Job won’t run on demand. I saw Daniel and Caspar’s response to this in another thread, and it is clear that the new ‘test’ invoked during the ‘Run now’ command, is preventing a lot of users from effectively testing their backups immediately. I see the same error as everyone else: “The HTTP response test get a false http status (401)”
The second failing case is more difficult. It targets Azure storage and the credentials seem to be intact. The error log is not as helpful. But on that host I am able to execute a ‘Run now’ which is helpful if testing after making changes to backup settings.
I’ll add more information here if I can resolve the second site issues.

My only other comment is that you cannot make a bold statement like “tens of thousands of sites must be working” because of the trickle of issues popping up here. IMHO, most websites are pretty poorly maintained and errors like a backup not working may go completely unnoticed for weeks.

I want to add to this discussion, but the only helpful response at this point is for the development team to be transparent about their latest release. Caspar and Daniel have been replying intermittently to various complaints in different places. We need a comprehensive listing of issues and a method of following them (ala Github).
My observations to add to this forum are from two production sites, on totally different hosts, where the BackWPup failed in different ways as soon as I updated the plugin from 2.17 to 3.06
In the first case it seems to have lost the authentication information for a Dropbox account. Easily remedied (the error log made it clear), but then I was unable to test. Like others, the Job won’t run on demand. I saw Daniel and Caspar’s response to this in another thread, and it is clear that the new ‘test’ invoked during the ‘Run now’ command, is preventing a lot of users from effectively testing their backups immediately. I see the same error as everyone else: “The HTTP response test get a false http status (401)”
The second failing case is more difficult. It targets Azure storage and the credentials seem to be intact. The error log is not as helpful. But on that host I am able to execute a ‘Run now’ which is helpful if testing after making changes to backup settings.
I’ll add more information here if I can resolve the second site issues.

My only other comment is that you cannot make a bold statement like “tens of thousands of sites must be working” because of the trickle of issues popping up here. IMHO, most websites are pretty poorly maintained and errors like a backup not working may go completely unnoticed for weeks.

I found an ‘answer’ to my second problem with Azure blob storage. In another thread here.
Azure Blob Storage

It’s not the dependency issue, which Daniel said he fixed, but the second issue of the backup taking too long. This results in an SSL connection error. The backup running log displays it’s progress bars(using Run now) and indicates no problem, but the error is in the log.

Like the OP of this issue, I had tested with a smaller backup (db only) and found that the same parameters for the job, same Azure container etc, does WORK. So, I guess all I have to figure out why the connection gets lost. Daniel seems to indicate in his response that he will have to get a proper callback on the upload, but why? How significant of a change has been made in the source code of WPbackup to make this happen? Azure storage has not changed at all. My backups using 2.17 were working fine just 2 days ago.

Seems to work ok now. Here’s how:
In BackWPup Settings>Jobs I changed 2 things:
“Checked” Restart the job on every main step on a running job
“pclZip” Method for creating ZIP archive
Re-ran the job, and the job seems to run error-free now.
Thanks to all of you above for the help.

Seems to work also on my Installation!

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

My pleasure. ??

@caspar
Do you plan to release a further Version without this “bug”?

I hope so, because I enjoy this plugin, it’s the first backup-plugin which was running without Problems (V2.17) and has all basic features I need.
So I hope you will come back in some days with a new version but quality as before.

good luck!

Doesn’t work since update to version 3.0.4.

Uninstalled and re-installed working version 2.1.17 from back-up folder.

Yet another unasked for update that makes us lose our time.

For a quiet web and efficient websites, say NO to unending updates !

Code isn’t poetry – and true life is beautiful.