Support

Please post your backup log. We can guess, but it's better if we act on evidence ;)

Meanwhile, try manually excluding the backup output directory. Does this help? If not, well, ZIP and attach the backup log on your next post so that we can find out what happened.

OK, my hunch was correct, JoomlaPack is trying to backup the backup file, leading to an error. The problem is your output directory. You have selected the site's root as the output directory, but this won't work!

Please go to JoomlaPack's configuration page and click the "Reset to default" button, next to the output directory. This will reset your output directory to the one inside the component's directory, namely administrator/components/com_joomlapack/backup. Ignore the warning about using the default output directory, it is not an error, it's just a reminder. Then proceed to backup your site. Normally, you should have no further problems.

This is the generic Apache error log. It logs missing files as errors. There's nothing to be worried about in there, but there is also no evidence of a PHP failure, most probably because your last backup worked fine. As soon as you have another failed backup, you can repeat the error log posting routine so that we can have a look at the backup issue.

Just for the record, I don't it's a SQL query limit, because it would always end up with a 500 Internal Server Error, no matter what, and would make your site inaccessible for about one hour (that's how query limits work). Another probable cause is a backup timeout, or too many web page requests happening in a very short time. The latter is addressed in 2.4.1, so my best guess would be a timeout error which can be worked around in many ways - if we have both the server error log and JoomlaPack's backup log. You can try setting the backup mode to Javascript Redirects and, if it fails again, just post your backup log and server error log file.

Finally, the [ROOT] tag is JoomlaPack's shorthand for your site's root. It's explained in the, admittedly VERY long, JoomlaPack Configuration documentation page. To cut a long story short, on your site [ROOT] is replaced on-the-fly with (/home/globalso/public_html, which is the absolute directory to your site's root. No worries on that.

This is crazy. There is no error related to the backup logged, the backup fails on different operations and there is no specific error. I guess this is a server configuration, so we'll try to work around it the hard way.

First, switch JoomlaPack to Easy Mode using the first icon in the Control Panel. Next, please go to Configuration and choose the Optimistic settings mode. Save the configuration and go back to the JoomlaPack Control Panel. Then, switch back to Expert Mode and re-run a backup.

If it fails, DO NOT click the suggestion to switch to Balanced mode. Instead, go to the Configuration and set the "Minimum execution time per step (in milliseconds)" parameter to 5000 - it's under the Advanced pane.

If all else fails, you might want to give me Super Admin access to your site (PM me details) so that I can try all possible workarounds.

You're welcome :D

Generally speaking, the default settings work great with a little bit of tweaking on even the most restrictive hosts. Version 3 (which will be called Akeeba Backup 3.0 due to a name change) will make it even smoother, by using a more precise method of avoiding timeouts, even on very large files. So far, I have been able to backup files of up to 3.3Gb using a pre-alpha version on live sites :D