Support

I understand that you are using Joomla's Scheduled Tasks to schedule your backup.

Can you please send me a screenshot with the task's configuration?

Moreover, please tell me how are scheduled tasks triggered: Lazy Scheduling, Web CRON, or CLI CRON?

Finally, please tell me how the scheduled tasks trigger is configured — I need to know how often the trigger is executed.

You cannot run a test for the backup task. The backup task is a "resuming" task which means that it will stop before it finishes. Next time Joomla tries to run tasks it will run it again and it will resume. This will keep happening until the backup is complete. You can already see this behaviour in your log file. There's a certain amount of time between Akeeba Backup saving its state and the next step starting. That time is how long it took between the end of a task execution to the next task execution by Joomla.

The test button only runs the task once, the task returns with an exit code which basically says “I am not done, I will resume next time you call me”, hence Joomla reporting a warning.

What I really want to know is the last two bits I asked you last time and which you didn't provide a reply on:

> Moreover, please tell me how are scheduled tasks triggered: Lazy Scheduling, Web CRON, or CLI CRON? 
> Finally, please tell me how the scheduled tasks trigger is configured — I need to know how often the trigger is executed.

This is important. If there is any way that the time between two subsequent task executions might be longer than 3 minutes (180 seconds) the next time the task tries to run it will consider the backup attempt "stale", it will mark the backup attempt as failed, and will not proceed.

> [09-Jan-2023 19:36:42] PHP Parse error: syntax error, unexpected T_CONST in /homepages/24/d248269769/htdocs/www/cli/joomla.php on line 11

This means that you tried running the Joomla CLI (cli/joomla.php) with a PHP version earlier than 7.4.

You need to contact your host and have them tell you what is the correct path to the PHP 8.0 CLI executable. I can tell you for sure that it's not /usr/local/bin/php8.0; this outputs "X-Powered-By: PHP/8.0.26" which tells me immediately that this is the CGI/FastCGI binary. The Joomla CLI application won't run when it detects that you're trying to use the CGI/FastCGI executable. That's why your test failed.

Once you have it, let's say /usr/bin/php8.0-cli, you can create a CRON job for a command line like this

/usr/bin/php8.0-cli /homepages/24/d248269769/htdocs/www/cli/joomla.php akeeba:backup:take --profile=1 --description="Sauvegarde hebdomadaire"

This will work and it will be reliable.

The only asterisk is that your host may have limited your per-process CPU time. You can find that out by running ulimit -t in your SSH console. If it replies with unlimited you're golden. If the number it replies with (which is in seconds) is lower than the time your backup needs to run you'll have to ask your host to increase your user's CPU time limit in their /etc/security/limits.conf file.

As I already explained, when you see the output line "X-Powered-By: PHP/8.0.26" it means that you are using the PHP CGI/FastCGI executable which DOES NOT WORK WITH JOOMLA ITSELF (cli/joomla.php). You will need to use the PHP CLI executable. As I explicitly told you and as we have explicitly documented this is necessary and if you do not understand what this means you need to ask your host.

Kindly note the following facts.

1. The requirement for the PHP CLI executable to use the Joomla CLI application and, by extent, any third party command which can be executed through it including but not limited to Joomla's built-in Scheduled Tasks and Akeeba Backup's CLI backup command (akeeba:backup:take) is fully documented in the software documentation which is available free of charge and publicly (you do not need to be a subscriber or even have a user account on our site to read it).

2. Before subscribing you have indicated that you are fully informed on the product and unreservedly accept the Terms of Service. This means that you have read and understood the documentation and accepted the requirement of the Joomla CLI application as necessary. As a result what you stated in ticket 38287 is unacceptable.

3. Please note that the cli/joomla.php file is part of Joomla itself. It is not developed, or maintained by Akeeba Ltd. Akeeba Ltd has no say on its development and its features. We cannot accept responsibility for it, nor can we provide support for it beyond what I've already done here. If you do not accept how Joomla works that's your problem, but nobody can do anything about it, let alone us take the financial responsibility of your failure to follow a simple instruction ("ask your host").

4. You have been provided a valid solution to your problem which you refuse to follow. You are using your refusal to follow a simple instruction as a pretense to demand a refund on false grounds. As a result this ticket is closed and we will not reply to any future requests about this issue until you actually follow the very simple instruction we have given you: ask your host what is the path to the PHP CLI binary and use it in your command line.

Finally, please note that demanding a refund on a false pretense is in direct violation of our Terms of Service. This is a final warning.