Support

It's okay. I am sorry for the long and slightly hostile reply. We've had a few cases of fraudulent refunds in the past and we got to be very skeptical.

So, let me tell you what I really wanted to say with regards to your issue.

Once you have the PHP 8.0 CLI executable you'll be able to run the backup using the akeeba:backup:take command as long as the backup finishes within 1800 seconds (half an hour), including the time it takes to upload it to remote storage if you have configured that. Remember that your host gives you a CPU time limit of 1800 seconds as you discovered by running ulimit -t over SSH.

If the backup needs more time then that the backup will fail at approximately half an hour. I don't say exactly half an hour because CPU time and wall clock time are not exactly the same, there's usually a 5% to 10% difference (that's the time the system itself needs to process its own stuff).

If this happens don't despair, we CAN get it working using a Scheduled Task (Akeeba Backup - CLI Backup) and having the CRON job run every 5'. The actual schedule of the backup will be defined in Joomla's backend (the Scheduled Task itself). The CRON job will simply tell the backup to chug along. I will just need to tell you how to configure the scheduled task and the CRON job for the Scheduled Task. This is the real reason I implemented the scheduled tasks integration with Joomla 4: it allows us to give our clients instructions to overcome limitations imposed by the host on most hosts imposing such limitations. I have alluded to that in the documentation but I didn't explicitly state that so as not to unnecessarily confuse people trying to set up a scheduled task for the first time (they'd see the more complicated setup and would think that only the complicated setup would work, something which isn't true on the vast majority of servers and sites).

You're welcome!