That’s a pretty large backup, and if it is working fine on another, smaller site with the same host, then you are likely just running into resource limits.
A good way to work around this is to split the backup into 2-3 parts and see if each one backs up consistently. Then you can put them on alternate schedules so they don’t all run at the same time. You can use the ‘Excludes” functionality to accomplish this.
Kat
Hello katmoody,
Thank you kindly for your quick reply.
It’s a large backup, huh? There are a lot of duplicate images that are the root cause of the size. I think they were created using regenerating thumbnails plugin. There is no obvious way to safely delete them. Force regenerate thumbnails plugin managed to remove a lot of them, but not all.
My employer didn’t quite get the importance of regular backups… so I try to use your plugin instead. I’ve updated your plugin to the latest version. It now says “Backing up files…(instead of calculating size”
I will let you know by tommorow, thank you.
Turns out it was backing up files outside WordPress as well, which includes very large backups.
Excluding it won’t solve the problem, unless I’d exclude the uploads folder as well. Running a backup either failed with uploads folder or successful without it, will write a 100 MB+ debug log! It’s too large to analyze.
So you aren’t able to exclude the large files through the “Excludes” functionality? Maybe try and backup JUST the uploads folder and then everything else. Run it on two schedules at alternate times. Let me know if you’re able to do that at all?
Kat
Hello,
I’am able to exlude any folder. I will try to run two schedules at alternate times like you said. In the meanwhile, there’s something going on in the debug log:
PHP Warning: array_filter() expects parameter 1 to be array, string given in /xxx/htdocs/www/wp-content/plugins/backupwordpress/admin/schedule-sentence.php on line 130
And
WordPress databasefout Got a packet bigger than 'max_allowed_packet' bytes bij query INSERT INTOxxx_options
Backupwordpress creates a 100 MB+ debug log, which is so large that it can’t be opend for analyzing properly.
Hello katmoody,
Running two schedules didn’t work either.
Are you able to reach out to us via the support module? Last I knew, we didn’t have a debug log via our plugin. Where are you finding that log at?
Kat
