Support

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? No
Have I searched the tickets before posting? No
Have I read the documentation before posting (which pages?)? No
Joomla! version: (unknown)
PHP version: (unknown)
MySQL version: (unknown)
Host: (optional, but it helps us help you)
Akeeba Backup version: (unknown)

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:


Hi, I have two separate sites on the same server. The smaller site backup completes in about a minute (see attached log), although it generates a much bigger .jpa file than I expected.

The larger site does not complete. See the second log. It seems to be super-slow, and then spawns a second backup, and a third, and a fourth... Within a couple of hours, the server falls over because the disk is full. One day last week, the Akeeba log for the larger grew to 2.5GB.

I seem to have the same problem from the backend and from the command line.

Thanks.

Yes, I couldn't attach a CLI log file, because they are mega huge. I will work on reducing the size of the DB etc, and hopefully that should fix it.

For future reference, is there a way of aborting a cron job CLI backup once it has started? I had to re-boot the server.

Yes, I could do that. Just kill the cron process? Or are there other process which would then also need killing?

Thanks.

OK. Hopefully it won't be needed, but thanks very much for your prompt help. Jeremy.