Support » Plugin: UpdraftPlus WordPress Backup Plugin » Backups bring my site down

  • Resolved cag8f

    (@cag8f)


    Hello. I’m having an issue with Updraft backups requiring several hours to complete, and bringing my site down during the process. I opened a ticket about this (ticket here), and one of your devs and I were making a lot of progress with troubleshooting. But he seems to have disappeared in the final step. Is there any way someone can take a look at my most recent log file (log file here) and let me know your thoughts on the possible issue?

    Specifically, the dev had suggested I enable the alternate cron in WordPress, and try the backup again. I did so, but the same issues are occurring.

    If you want to continue this in the other ticket, I am happy to do so.

    Thanks very much.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor DNutbourne

    (@dnutbourne)

    Hi,

    Apologies for the delay. It appears that the previous thread was lost in the shuffle.

    From the log, it appears that the zipping process is being killed off early by your server.
    This could be due to a timeout or the site hitting a resource cap.

    Please could you ask your hosts to check the PHP and server error logs for the site? These logs should contain a record of any timeouts or memory limit errors.

    I would also recommend trying a backup with the ‘Split archives every’ option set to 25MB.

    >> Apologies for the delay. It appears that the previous thread was lost in the shuffle.

    OK no problem.

    >> Please could you ask your hosts to check the PHP and server error logs for the site? These logs should contain a record of any timeouts or memory limit errors.

    I’ve already checked the PHP error log, and there is nothing written to it during these backups. And I’ve asked my web host (name.com) if there are any other logs they can check that would contain entries during these backups, and so far they have said no, the only log they have is the same PHP log.

    >> I would also recommend trying a backup with the ‘Split archives every’ option set to 25MB.

    In the other thread it was suggested that I lower that from 400 MB to 100 MB. I tried that, and it didn’t really change much. But I’ll try lowering it again to 25 MB and let you know of the results. I’ll post back here.

    >> From the log, it appears that the zipping process is being killed off early by your server. This could be due to a timeout or the site hitting a resource cap.

    OK got it. As I mentioned in the other post, during these backups, several of my server resources are indeed hitting the resource limit. Specifically, “Physical Memory Usage” jumps from 0 to its max of 256 MB, and “I/O Usage” jumps from 0 to its max of 1 MB/s. They remain at max levels for the entire duration of the backup, then fall back down to zero. If I raise this with my web host (name.com), they will simply point to your plugin and say it is clearly not optimized. I want to be clear that I don’t agree with that–I think there is perhaps a separate issue causing these resources to hit their limit. But if my web host comes back at me with that argument, how can I respond? Are there any other tests we can run, or troubleshooting steps, to counter that argument? I know that I’ve used your plugin on many other sites (on other web hosts), without issue. But name.com support won’t really accept that. They are unfortunately not very helpful.

    Thanks.

    Plugin Contributor DNutbourne

    (@dnutbourne)

    Hi,

    Were you able to run a backup at a 25MB split?

    cag8f

    (@cag8f)

    > Were you able to run a backup at a 25MB split?

    I did. The total time of the backup was reduced to ~2 hours, but my site still went down two times during the process. I’d like to resolve that.

    What about the questions I asked you in my previous comment? Are you able to reply to those?

    Plugin Contributor DNutbourne

    (@dnutbourne)

    Hi,

    Apologies for the delay.

    I’m afraid that, configured as it is, UpdraftPlus is as optimised as it currently can be.
    Unfortunately, backups are inherently high-resource tasks.

    I believe that the site going down is likely to be due to the I/O limit being reached.
    You may need to ask your hosts if it is possible to upgrade this.

    OK then. I’ll try to troubleshoot the issue in another way. Thanks for the help. We can consider this resolved.

    Actually hold on. I know you said it’s not terribly unusual for the I/O limit to be reached. But what about the 2 MB RAM limit? Every backup hits that limit as well. Any idea why? Is that not uncommon with backups?

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.