Support

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes (need a better search tool, to ONLY search tickets.
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.6
PHP version: 5.3.6
MySQL version: 5.0.95
Host: Blaanye
Akeeba Backup version: 3.6.1

Description of my issue:
I've set up two profiles, one takes backup locally (default), one takes backup to dropbox.
I've set the profile to keep 4 backups or 4 GB of backup, but looking in the log, I have 15 files and 10 GB of backup.
I've attached the quota settings below.

Sorry for being unprecise, the dropbox profile seems to work fine, after you pointed my missing the two ticks as you did again here :-)
It's the local quota, which this profile is supposed to handle (default/local).

Where do I find minimum backup age? I can see maximum?

I've searched the docs, but don't see what you mentioned with "minimum backup age"?

The profile I've set up should handle local storage.
I only have two profiles, local (1), dropbox(2).

Those settings are the ones I desire,yes.

I did read the documentation, and I know about MAXimum age, but you said MINimum age????
I know the obsolete is merely a showing of backups taken at a specific time and the time it took.

The jobs with Daglig lokal backup / Daily local backup is with profile 1

The command the cron is executing every day is:

/usr/local/bin/php /xxx/cli/akeeba-backup.php --profile=1 --description="Daglig lokal backup" >/dev/null 2>&1

Not much to see there,as it's set to warnings and errors only, should I rerun the backup with another error level? And if so, which level do you want?

Quite a bit more info in it today...

An hour, wow that IS long.
I doubt the hotel provider will extend it to that long, and I guess it's only a temporary solution until the backup takes longer...
Couldn't the script close the connection sooner, and reopen it?

Usually my provider is very responsive, apart from keeping the mysql connection open for extreme periods, what else can be done in the mysql, so it wont deny the connection?

I just tried running the profile from Backend, and that completed without errors, and also cleaned up in the files and everything.

I'm going to test with a cron via frontend backup.

I've tried running from the frontend via cronjob, and that also works.
I have a modified php.ini in my root directory, I guess that could affect things, it looks like this
post_max_size = 50M
upload_max_filesize = 50M
max_execution_time = 600

When I backup from frontend/backend, the log looks like this in the beginning:
[120815 12:00:02] --- System Information ---
[120815 12:00:02] PHP Version :5.3.6
[120815 12:00:02] OS Version :Linux
[120815 12:00:02] DB Version :5.0.95-community
[120815 12:00:02] Web Server :Apache/2.2.21 (Unix) mod_ssl/2.2.21 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
[120815 12:00:02] PHP Interface :cgi-fcgi
[120815 12:00:02] Joomla! version :2.5.6
[120815 12:00:02] Wget/1.11.4 Red Hat modified
[120815 12:00:02] Safe mode :0
[120815 12:00:02] Display errors :
[120815 12:00:02] Error reporting :
[120815 12:00:02] Error display :off
[120815 12:00:02] Disabled functions :
[120815 12:00:02] open_basedir restr.:
[120815 12:00:02] Max. exec. time :600
[120815 12:00:02] Memory limit :128M
[120815 12:00:02] Current mem. usage :14655292
[120815 12:00:02] GZIP Compression : available (good)
[120815 12:00:02] JPATH_BASE :<root>
[120815 12:00:02] JPATH_SITE :<root>
[120815 12:00:02] JPATH_ROOT :<root>
[120815 12:00:02] JPATH_CACHE :<root>/cache
[120815 12:00:02] Computed root :<root>
[120815 12:00:02] Output directory :/home/dkdbdk/backup

When it's startet from CLI, it looks a bit different in the settings:
[120815 02:30:01] --- System Information ---
[120815 02:30:01] PHP Version :5.3.6
[120815 02:30:01] OS Version :Linux
[120815 02:30:01] DB Version :5.0.95-community
[120815 02:30:01] Web Server :n/a
[120815 02:30:01] PHP Interface :cli
[120815 02:30:01] Joomla! version :2.5.6
[120815 02:30:01] Safe mode :0
[120815 02:30:01] Display errors :
[120815 02:30:01] Error reporting :E_ERROR | E_WARNING | E_PARSE | E_CORE_ERROR | E_CORE_WARNING | E_COMPILE_ERROR | E_COMPILE_WARNING | E_USER_ERROR | E_USER_WARNING | E_USER_NOTICE
[120815 02:30:01] Error display :off
[120815 02:30:01] Disabled functions :
[120815 02:30:01] open_basedir restr.:
[120815 02:30:01] Max. exec. time :0
[120815 02:30:01] Memory limit :32M
[120815 02:30:01] Current mem. usage :3819756
[120815 02:30:01] GZIP Compression : available (good)
[120815 02:30:01] JPATH_BASE :<root>
[120815 02:30:01] JPATH_SITE :<root>
[120815 02:30:01] JPATH_ROOT :<root>
[120815 02:30:01] JPATH_CACHE :<root>/cache
[120815 02:30:01] Computed root :<root>
[120815 02:30:01] Output directory :/home/dkdbdk/backup

There is a difference between memory limit, execution time og error reporting, though I have no idea why that would affect it.

Can't make the alt script work properly, the guest counter goes haywire.
I'm going to use the frontend backup, as that seems to work perfectly.
It seems that my host likes it better when the connection are closed/opened for each step.
I also tried making the php command use my own php.ini, but that didn't help.