Support

The FTP upload code hasn't been changed for well over a year, and definitely not between the last three versions.

Your log file shows that Akeeba Backup was connected just fine to your FTP server, but after exactly 90 seconds the upload failed. 90 seconds is the default timeout for FTP uploads in PHP, so this tells me something important.

Your backup archive is 127341973 bytes, i.e. 121.44 MB big. To upload such a big file within 90 seconds you'd need a transfer speed to the remote host of at least 1.4 MB/sec which, taking into account overhead and packet losses, would require an at least 15 Mbps connection. In our experience, FTP uploads usually top out at around 10 Mbps on most server combinations, with some being significantly lower than that. This would indeed cause a timeout during the upload just because your backup grew “big enough” to not make it over a single FTP transfer.

As noted in the documentation, we recommend using a smaller Part Size For Split Archives in this case. Try using a Part Size For Split Archives around 50 MB to be on the safe side.

You can do that in the Configuration page of your backup profile. Find the Archiver Engine and look at the options below it. Find the Part Size For Split Archives and set it to 50 MB. Save & Close, then take a new backup.

Note that this will split your backup into three files with extensions .jpa, .j01, and .j02. You will need both files to be present to restore it. Kickstart will only show you the .jpa file, but it knows this is a multipart backup archive, i.e. it will automatically look for the .j01 file (which is, in fact, the first file in the backup set) and .j02, and extract the backup archive files in the correct order.

Scheduling backups requires something to tell them to start, and keep going until they are done.

If your host doesn't have real CLI CRON jobs but does offer URL-based CRON jobs you can use either the front-end legacy backup option (if your host supports redirections), or Joomla! Scheduled Tasks with a URL-based CRON accessing Joomla's task scheduling URL every minute or so. I have documented all of that thoroughly; unfortunately, Joomla didn't document its very useful and robust Scheduled Tasks system, a big shame if you ask me.

If your host has absolutely no CRON support –neither real CLI CRON jobs, nor URL-based– you still have a few options left.

You can use an installation of Akeeba Panopticon on a different host, which does support CRON jobs, to schedule remove automatic backups.

You can use Akeeba Remote CLI on an always-on machine, for example a desktop or office/home server, to run backups remotely.

You can use a third party service such as Watchful to run scheduled backups remotely.

Last but not least, a different host. It's 2024. The number of sites which can reasonably operate without any kind of task scheduling is dwindling fast. If the host you're one can't keep up with the times, maybe it's time for you to move to a different host. I recommend Rochen. They do offer us free hosting for this site, but I do pay them out of my own pocket at full price for all of my personal sites; I'd never recommend anything I am not comfortable spending my own money on.

Yes, you can schedule backups through that third party service :)