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. Click here for more details.
Additionally, consider the following:
Store any of your sites files that are non-essential at a third party location, and exclude them from the backup. You can take this as far as storing old uploads directories, for example, storing your uploads from 2014 & older on a third party location, and then excluding them from future backups.
Let me know if the above info helped you get any successful backup going or if I might need to go in and take a look to try and help troubleshoot further, okay?
Thanks!
Kat