Support

Akeeba Backup for Joomla!

#9305 Could not move the SQL dump to its final location

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Monday, 23 January 2012 15:12 CST

user56140
Mandatory information about my setup:

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

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: I was successfully running Akeeba backup for some months. During the last week or two backup has not worked. The initial problem was that it started, gave messages saying that all the files were being backed up, then froze when it got to updating statistics. I tried several times and waited 30 minutes longer, but nothing happened. I tried various remedies in the documentation, such as re-running the config. wizard, re-saving the file, but same result. I then tried just backing up the data base and got the message 'Could not move the SQL dump to its final location'. Even though I thought I had previously backed up files I cannot see any in the backup directory.

nicholas
Akeeba Staff
Manager
Akeeba Backup 3.3.1 is no longer supported. Please upgrade to the latest release, which is 3.3.11 at the time of this writing.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user56140
Sorry, it was a mis-typing. I am actually running 3.3.11.

nicholas
Akeeba Staff
Manager
I am half-blind myself. I opened your log and misread 3.3.11 as 3.3.1. Doh!

OK, the issue looks like you're running out of disk space. Can you try removing one or two of the oldest backups? If this doesn't help, try emptying your tmp directory. These are temporary files which can be safely removed.

If this doesn't work, try two different sets of configuration options:
SET 1 ---
Minimum execution time: 4 seconds
Maximum execution time: 2 seconds (yes, max is less than min)
Runtime bias: 50%
SET 2 ---
Minimum execution time: 1 second
Maximum execution time: 25 seconds (yes, max is less than min)
Runtime bias: 70%

If this still doesn't help, please ZIP and attach your new log file and tell me which one of the two sets of options you used.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user56140
I have tried several things.

1 Gone through the system and removed tmp files as well as old backups. Strangely, there were files from the weekend labelled backup, even though the backup process never finished successfully. These were files of 400MB. My Joomla database is almost 800kb, so that seems to be the database plus files, as configured.

2 Checked my disc quota on the server. I am at about 7%. Nevertheless, I have asked my service provider to check the disc space as there were space problems with other applications over the weekend.

3 Changed the parameters to set 2 and tried a full backup. It froze as before when reaching the gathering statistics stage. Log file 1 attached.

4 Tried srunning just a database backup with set 2. 'Could not move SQL' message occurred. Log file 2 attached.

5 Tried running backup with set 1 and set to just database. Same error as in 3. Log file 3 attached.

nicholas
Akeeba Staff
Manager
Please send me a Personal Message (I am user "nicholas") with the following information:
- A link back to this thread. Without it I won't know why you're sending me the PM.
- The URL to your site's back-end
- Super Administrator connection information
- FTP connection information; not strictly required but will help me to have it
and give me 24 hours so that I can take a look myself.

Thanks!

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user56140
Nicholas

Before I create more work for you you might like to read this reply from my web hoster.

"We run a program to automatically stop SQL queries that take too long to run. Currently it's 20 seconds, if a query runs for more than 20 seconds it'll be killed (as long as it's not a UPDATE/DELETE/INSERT query). That program hasn't been running since Thursday, however, so if you've been having backups failing after that it'll be something else. The next thing to look at is how long PHP processes can run for which is 30 seconds. If it takes that long (or longer) it may be interrupted."

Should I set any of the parameters differently to take account of this, or do you still want me to end you the information by PM?

Thanks
Stuart

nicholas
Akeeba Staff
Manager
No query is running for over 20 seconds. In fact, according to the log, the SELECT queries used to dump the database run for mere milliseconds. The execution time never reaches 30 seconds. Remember the values you set? They control the maximum amount of time each page load will take.

So, yes, please do send me the PM.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

nicholas
Akeeba Staff
Manager
Thank you for your PM. I tweaked the settings to use the database of the filesystem to store temporary files and now the backup completes reliably.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user56140
Thank you for your fantastic support. That installation is now working. I have never come across such speedy and comprehensive support.

Stuart

nicholas
Akeeba Staff
Manager
You're welcome :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!