Backup process interrupted/not finishing

@bws-online
I think there is a really big file(which larger than your maximum memory limit), maybe there are backup folders of other plugins, please exclude them from the backup list then try again, or you can try to change the backup archive type to tar instead of zip.
I hope that it could help ^^

Thanks @duongcuong96.

I’ll explore further (didn’t find any really big files or backups for other plugins on initial inspection). It happens almost immediately, though, and works fine on the SECOND manual launch — does that still sound like it’s an issue with a really big file?

Where do I find the limit for file size?

@bws-online
if not the case, sometimes the server just kill the backup process, so the job is just stopped there, the reason is server resource limit reached, I think you could try to reduce server load to medium / maximum in BackWPUp -> Settings -> Jobs

Also, enable debug log ( BackWPUp -> Settings -> Logs -> set logging level to debug(not translated) )

After that, run the job again, check the log and maybe you could see which folder caused the job hanging.

So are you saying to set “Maximum Script Execution Time” to 0? (Right now it’s 30, so it feels like that’s not the issue since it’s stopping at 0 or 1 second, not in 30 seconds.)

I enabled the log — it gets through the database backup (I see the lines for the database table details) and then ends with:

[25-Jun-2021 09:27:31] Added database dump "database_name.sql" with 29.98 MB to backup file list
[25-Jun-2021 09:27:31] Database backup done!
[25-Jun-2021 09:27:31] 1. Trying to make a list of folders to back up …

As before, after I’ve done this one time, if I click to run again, it runs fine. I’ve seen this across multiple sites (my own and clients’). Is there something that would be triggered after the first run fails that would then allow the second run to go smoothly? (And since an automated run only happens once, it’s not working.)

I just did a test — set up 2 jobs (copies of the current schedule job) — one to run at 9:35, the other at 9:40. The first one did the 0 second run like above, the second one completed. So until this gets fixed, at least I have a way that might work for automated backups. Hope that helps others who might be having a similar problem.

@bws-online
hmm at the first run, could you try to just reload the page again just to check if the job running despite the log said job completed?
Thank you

@duongcuong96 I reloaded the page and the job restarted, but I don’t think it was running — as before, the first run ended with the same results as I described above, and then a second job was listed (and completed fine).

@bws-online
hmm, this strange to me, but happy to hear that the issue has been resolved ^^

I don’t think I’d consider this resolved? I figured out a workaround to fix a problem — efforts to troubleshoot and fix the problem would still be appreciated.

@bws-online
I’m not sure if it is related, but maybe you could try to enable alternative cron, then run the job again to see if the issue is fixed.
Here how to enable WP alternaive cron:
modify wp-config.php ( you can find this file in your root directory ), and BEFORE the line:
/* That’s all, stop editing! Happy blogging. */
add this line:
define('ALTERNATE_WP_CRON' , true );

since we haven’t heard back from you, I’m going to mark it as resolved.
If you’re still having problems, feel free to let us know ??