WordPress.org

Ready to get started?Download WordPress

Forums

BackWPup Free - WordPress Backup Plugin
[resolved] BackWPup not working after upgrade (45 posts)

  1. FNGeditor
    Member
    Posted 1 year ago #

    This plugin does not work after upgrade from ver 2.1.17. Both releases of the 3.X version get to 70% and hang there. My sites running the earlier release work fine.
    Fortunately, I tried the backup after updating my first site and did not mess them all up.
    Hopefully, this issue is being actively addressed and a new release will be provided soon. No backups have been completed successfully for the last two weeks.

    http://wordpress.org/extend/plugins/backwpup/

  2. FNGeditor
    Member
    Posted 1 year ago #

    Just to update on the broken BackWPup plugin, I continued to see what I could do to resolve my failing backups. No resolution I could find by adjusting settings on the new interface. Backups still hang. The reviews indicate that this update is a failed update pretty much all around.

    Restoring the plugin from a previous backup did not seem to work for some reason, and the last version I had downloaded was version 2.1.13 (the latest before version 3.0 was 2.1.17). I did find it on WordPress for download though (see below).

    For those who would like to roll back to a functional version, my temporary work around was to confirm my manual settings (directories to exclude, backup location, etc), remove the plugin (be sure your backup location is not in a directory under the backwpup folder, or you will loose those backups)and re-install the plugin by downloading the earlier version (you can pull from the WordPress archive at: http://downloads.wordpress.org/plugin/backwpup.2.1.17.zip ). You will have to reconfigure after install, and you will loose your logs, but the earlier backups will still be available if you observe the note above.

    Hopefully this plugin will be fixed soon, but be sure that I will try on a test site before upgrading BackWPup in the future.

  3. fredericsidler
    Member
    Posted 1 year ago #

    Same for me after upgrading to 3.0.4. Nothing works anymore and no logs.

  4. alanudi
    Member
    Posted 1 year ago #

    I'm getting major timeouts and errors now. Never had a problem before. The log also doesn't seem to work correctly. I cannot see the "live log" like before, now I have to "hope and pray" the job finished, so I can see the log. However, considering I'm getting timeouts that take an hour or more, I have no idea if the job even started, because it's not in the log list.

    The errors I am now receiving as of 3am (monday) after a full weekend of smooth backups that all run automatically:

    [11-Mar-2013 03:16:28] Compression method is ZipArchive
    [11-Mar-2013 04:17:56] WARNING: Job restart due to inactivity for more than 5 minutes.

    &

    [11-Mar-2013 04:17:56] ERROR: Can not add "wp-includes/js/jquery/ui/" to zip archive!
    [11-Mar-2013 04:17:56] ERROR: ZipArchive returns status: (ER_DELETED) Entry has been deleted

    Thanks for your help!

  5. glueckpress
    Member
    Posted 1 year ago #

    Hi FNGeditor,

    +1 for posting your workaround. :) 3.0.5 has been released today, haven you tested it? If the issue persists, please consider posting a log file, so we can work on it.

    Thanks,
    Caspar

  6. alanudi
    Member
    Posted 1 year ago #

    Hi! I updated the plugin today, but I'm still unable to get the jobs to run.

    I have 2 quick questions that might answer my problem...

    First some background info.... It used to be that I could hit "Run Job" and the log would pop up and I could watch the backup log live as the job runs. However, after the last week of updates, the log doesn't pop open any more. This is a problem because, even though it says Job "Job-Name" started, there is not a log afterwards, and I don't know if it even happened.

    My question is: Was the live log removed from WPBackup intentionally? Or is this an indication that something is wrong on my end?

    Thanks so much!
    Alan

  7. ZeroGravity
    Member
    Posted 1 year ago #

    @alanudi I am having the same problem.

  8. fredericsidler
    Member
    Posted 1 year ago #

    Just upgraded to 3.0.5 and nothing happens. I just tried a DB backup sent by email. Nothing. The test email works, but when I lauch the job, no terminal window with progression is displayed. The only thing that is displayed on the top is "Job "DB Backup" started."

  9. alanudi
    Member
    Posted 1 year ago #

    Hi, just an update on my status....

    Last night my daily automatic backup did successfully complete, and the log appears to me totally normal.

    However, I am still unable to manually force a backup. It say the job started, but there's no way to tell if that's actually true.

    I also created a new backup job that doesn't run automatically. I hit "run job" and it says it started, but there's never any log. Under "last run" it says "never".

    Thanks! I hope you're having good luck sorting all the work out.
    Alan

  10. Caspar
    Member
    Plugin Author

    Posted 1 year ago #

    @Alan You should be able to see a log at "Logs" right in the BackWPup admin menu. Can you post a log file here?

    @fredericsidler Please open a new thread an provide some details, i.e. a log file of the failed job.

  11. FNGeditor
    Member
    Posted 1 year ago #

    Just an update to all... I just installed the 2.1.17 plugin on a test site of mine, configured and executed BackWPup. It ran fine with and execution time of 66 sec.
    After upgrading to the latest (ver 3.0.6), the manual backup fails still. I was all excited when it passed 70% (after creating the Ziparchive), but hangs at 75%. I didn't bother waiting until it timed out, but this is the step it always seems to hang at:

    [14-Mar-2013 17:23:13] 1. Trying to create backup archive …
    [14-Mar-2013 17:23:13] Compression method is ZipArchive

    Plugin still fails to function properly. 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.

    In the meantime, I would have to say the plugin update is still broken.

  12. edwinkort
    Member
    Posted 1 year ago #

    My vote also. Above 2.1.7 the plugin is broken.

  13. RogerWheatley
    Member
    Posted 1 year ago #

    You will also find that the backups are password protected when you are able to get the upload to Dropbox working. What are the developers hiding?

  14. Caspar
    Member
    Plugin Author

    Posted 1 year ago #

    @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.

  15. FNGeditor
    Member
    Posted 1 year ago #

    Anyone reviewing this thread may be interested in the following update involving BackWPup not working after the 3.x.x release. I have really liked this plugin to provide automatic backups of my website, and therefore spent some time trying more experimenting on a test site today (3/19/2013).

    Background on my problem:
    Version 2.1.17 works fine... no problems and backs up in about 1 minute.
    Upgrade to any 3.x.x version gets to creating ZipArchive and just hangs around 70-75% depending on version and other backup settings.

    I tried just about every setting I could, and finally found one that seems to be the culprit on my site. The problem in my case appears to be with the ZipArchive compression function. If the plugin is set for "Auto" or "ZipArchive", it tries to make a ZipArchive type of backup and hangs. If changed to PclZip, it works every time in a little less time than the previous version.

    To resolve issue with timeout on backups, try this:
    • Under "BackWPup" , select "Settings"
    • From the "BackWPup Settings" Menu, select "Jobs" tab
    • From the Jobs tab, look for "Method for creating ZIParchive" and change to "PclZip"
    • Save your settings and try it again

    I'm not sure about some of the other new settings, and not sure why the auto select function defaults to ZipArchive since the previous version of BackWPup used PclZip for backups, but my main goal was to make it work. I look forward to the next update and hope it resolves this bug.

  16. Giuliano
    Member
    Posted 1 year ago #

    Hi,

    First, this is probably the best backup plugin out there, but it looks like there are some issues that need to be ironed out. I have the same problem as others above.

    I have 4 WP websites hosted on HostGator and one company website hosted on different host. All were working great with version 2 until I upgraded to plugin version 3. Since then all of them are exhibiting exactly the same issue. They just hang at 50%. According to the log from my company website job hanged for more than 4000 seconds. Non of workarounds mentioned above helped with the issue.

    This is the log from one of them. Please note that others are pretty much the same. For security reasons I posted just a last few lines. There were no errors before these lines.

    [20-Mar-2013 10:13:28] Database dump done!
    [20-Mar-2013 10:13:28] 1. Trying to make a list of folders to back up …
    [20-Mar-2013 10:13:28] 346 folders to back up.
    [20-Mar-2013 10:13:28] 1. Trying to create backup archive …
    [20-Mar-2013 10:13:28] Compression method is PclZip
    [20-Mar-2013 10:17:13] ERROR: Aborted by user!
  17. FNGeditor
    Member
    Posted 1 year ago #

    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.

  18. Giuliano
    Member
    Posted 1 year ago #

    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.

  19. Giuliano
    Member
    Posted 1 year ago #

    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.

  20. Giuliano
    Member
    Posted 1 year ago #

    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.
  21. eugk
    Member
    Posted 1 year ago #

    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.

  22. Giuliano
    Member
    Posted 1 year ago #

    @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?

  23. delaneybill
    Member
    Posted 1 year ago #

    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.

  24. delaneybill
    Member
    Posted 1 year ago #

    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.

  25. delaneybill
    Member
    Posted 1 year ago #

    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.

  26. civalp
    Member
    Posted 1 year 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.

  27. freica97
    Member
    Posted 1 year ago #

    Seems to work also on my Installation!

  28. Caspar
    Member
    Plugin Author

    Posted 1 year ago #

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

  29. civalp
    Member
    Posted 1 year ago #

    My pleasure. :-)

  30. freica97
    Member
    Posted 1 year ago #

    @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!

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.