Plugin Version: 3.1.2
I'm using a host that has a I/O cap in place. When I run the backup on a small set of files, lets say database dump, it mostly works.
At the default settings:
It can crate a tar ball of around 35-40MB, then it stops. However, once it starts creating the tar.gz file it stops after 2-4 MB and the process just hangs. I do not see any errors. Changing PHP to 5.4 seems to make it worse, the process stops sooner.
Here is what the support guy says: "It looks like it may be getting killed due to hitting the I/O cap for a long duration. Is there a way to set the script to 'nice' the process so it does not run at high priority during the backup generation?"
I did try to set the script execution time to lower values, down to 9s. 8 seconds will lead to an endless loop where the script starts every seconds at some point. Setting it to 9s and the maximum setting for the server load reduction allows the tar ball to be created but the archive creation will then just stop after a couple of MB. Looks like that this part is the main issue at least on my host. Keeping the archive as a tar file will allow the plugin to finish the process.
The support guy recommended getting in touch with you, the plugin developer, to see if the server load can be improved (the I/O part via ionice maybe?) or if pigz could be used which can improve I/O usage. Maybe pigz can be added as a 3rd option to the archiving method setting?
I have this plugin running on other hosts and one has the exact same WP setup (WP version, plugins, obviously no I/O cap) and it runs fine, so I don't think this specific behavior can be blamed on other plugins.
Question: would the Pro version take care of the issue I'm facing here? Does it have additional settings when it comes to reducing the server load?