If backups are completing after you’ve excluded your uploads, and/or other large directories, this is usually an indication that your server is struggling to complete the backup.
This means that your server begins the backup process but gets killed before the backup can complete. This can be due to timeouts on your server, such as the PHP max_execution_time, but also some hosts enforce max CPU timeouts. When the backup script hits these limits the script is killed.
It’s not a permanent solution to have your uploads excluded from the backup as they’re typically important parts of your site.
You have a couple different paths to correct this issue and hopefully get those backups completing.
Increase your server limits
In your php.ini (If you’re not sure how to make changes to your php.ini, your host may have more information to help you.) try making sure the following values are set to at least these minimums. If you have a large site think of increasing them further. (Contact your host to find out if they enforce PHP or CPU max timeouts).
memory_limit = 256M
max_execution_time = 120
max_input_time = 120
Check on Unix Zip Command
If you’re hosted on a Linux machine, check with your host that the Unix ZIP Command is installed on the server as this is the most performant method of creating backups. Ensure that it is available for the plugin to use and not blocked in some way.
Split your backups to reduce server load
You can split your backup into two (or more) different schedules. Check out our Knowledge Base article for more information: https://bwp.hmn.md/knowledge-base/splitting-backup-workload-using-excludes-functionality/
Let me know if the above info helped you get any successful backup going, okay?
Unfortunately, the above info did NOT helpe me get any successful backup going.
Please, read carefuly my original post :
“I have tried another backup plugin (UpdraftPlus WordPress Backup Plugin) and all files, INCLUDING “uploads” folder, are backed up in 12 seconds !”
BR,
Maciej
With this simply script (see below) I am able to backup ALL files in less then 30 seconds.
So, what is going on with your plugin ?!
BR,
Maciej
#!/bin/sh
#chemin absolu vers le r?rtoire racine du site ?opier
APPLI_HOME=”/kunden/homepages/…/MaciejRzeszutko/”
#chemin absolu o??archive doit ?e stock?une fois cr?
BACKUP=”/kunden/homepages/…/BACKUP/MaciejRzeszutko/”
#informations relatives ?a base de donn? de votre site internet
HOST=”……”
USER=”…..”
PASS=”…….”
BASE_SQL=”……”
#chemin absolu o?? bakup de la base de donn? est stock?emporairement
DATABASE=”/kunden/homepages/…/MaciejRzeszutko/dump.sql”
#Backup Base de donnee
mysqldump –opt -h$HOST -u$USER -p$PASS $BASE_SQL > $DATABASE
#on archive l’application ainsi que le fichier de dump MySQL dans le repertoire de sauvegarde
tar -cPhzf $BACKUP/date +%Y%m%d–date +%H%M.tar.gz $APPLI_HOME $DATABASE
#on supprime le dump MySQL
rm -f $DATABASE
Unfortunately, different scripts, commands and functions on servers mean that sometimes our plugin doesn’t work in some hosting environments even while other backup plugins and scripts do.
I’m sorry for any inconvenience, but happy you’ve found you have easy options that will work for your backup needs anyway.
Best of luck to you moving forward.
Kat
