Failed backup – stuck at pruning old backup sets

  • Resolved rkingisl

    (@rkingisl)


    10 months, 3 weeks ago

    Hello,

    I’ve been having trouble with my backups not finishing lately, and am not sure why. It seems to get stuck on the “pruning old backup sets” step, and hangs there for over an hour, repeatedly saying “next resumption…”. The archive split size is set to 25mb. I’ve added the “set_time_limit(300);” parameter to my wpconfig file, as outlined in your “Failed Backups” article, and have uninstalled the plugin, deleting the Updraft folder on my instance before reinstalling. I’m also not receiving emails about the incomplete backup, and am unable to tick the checkbox for admin emails, but I see that’s an ongoing issue. Any help would be very much appreciated. Here’s my latest log file: https://drive.google.com/file/d/1pzlzPzOac3IOdhQikgFQk-1P-Vu2oS7O/view?usp=sharing

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

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support pbevanudp

    (@pbevanudp)

    Hello,

    Thank you for providing the log file. Would it be possible for you to also provide a version with debug disabled please?

    Thread Starter rkingisl

    (@rkingisl)

    Thank you for your quick reply. Here is a log without debug enabled:

    https://drive.google.com/file/d/1LEFH5w9uF2tBlkShjW61URNsn_g9Rbsu/view?usp=sharing

    Plugin Support vupdraft

    (@vupdraft)

    Can you try adding the following to your wp-config.php

    define( ‘WP_MEMORY_LIMIT’, ‘512M’ );

    Thread Starter rkingisl

    (@rkingisl)

    Thank you for the reply. I’ve added the line to my wp-config file, but I’m getting the same errors:

    https://drive.google.com/file/d/17lRkWOOXwgF88yEJr2IYBXPr_fUrpbtd/view?usp=sharing

    Any help would be very much appreciated.

    Plugin Support vupdraft

    (@vupdraft)

    Would you be able to post your php error logs? these should be in the root of your site or you can ask your hosts for them

    Thread Starter rkingisl

    (@rkingisl)

    I can’t find the error logs in my wp-content folder. I’ve enabled them via the wp-config file, but I don’t see a “debug.log” file. Is there something else I need to do? And is it safe to post them in their entirety, or do I need to sanitize them first?

    Thanks again for the help.

    Thread Starter rkingisl

    (@rkingisl)

    Disregard my earlier message, I believe I’ve found the problem. months ago I changed the Google account that Updraft syncs with, and transferred ownership of the previous Updraft backup folder to this new user. I discovered, though, that the files inside this folder were still owned by the old account. So when Updraft was trying to prune the old backup sets, it wasn’t able to, since it didn’t have permission to delete the files. This is only just happening now that the old backups are old enough for pruning.

    I’m surprised that there is not a more-specific error message for something like this, though. Anyways, the last 2 backups have completed properly, so that’s good news.

    Thanks again for the help!

    • This reply was modified 10 months, 2 weeks ago by rkingisl.
Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Failed backup – stuck at pruning old backup sets’ is closed to new replies.