Support

Akeeba Backup for Joomla!

#8351 Multiple Database Definition Connection Problem

Posted in ‘Akeeba Backup for Joomla!’
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

user8566
I am a long time user of joomlapack and am familiar with the standard backup and restore procedures as well as general MySQL database connectivity. I did my first test backup & restore of Akeeba Pro and everything worked great. My next test (and the reason I purchased pro) was to try out the multiple database definition feature.

I am on a godaddy server which has host names like "mydatabase.db.4925033.hostedresource.com" rather than localhost. I popped over to the multiple database definition area, entered this info into the host field...entered the username/database names (which are one and the same on godaddy) into the appropriate fields, and "jos_" as my prefix (as the extra database i'm attempting to back up is another joomla database). I tried with and without specifying port 3306 (which i confirmed through PHPmyadmin is correct). I also tried with and without specifying a prefix in case that makes any difference.... no mater what I do I get "COM_AKEEBAUI-MULTIDB-CONNECTFAIL Could not connect to MySQL" when pressing the "COM_AKEEBAUI-MULTIPLEDB-TEST button.

Any suggestions are greatly appreciated!

dlb
I don't know the answer to this one, but I have a guess. Try it without the "prefix" field. I haven't seen any docs on this yet but I'll bet the prefix is for hosts that prefix the database and user name with the host account name. GoDaddy doesn't do that. JoomlaPack didn't do anything with the table prefixes on multiple databases and I'll bet Akeeba doesn't either.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user8566
Thanks for the suggestion but I tried with and without specifying the prefix and neither way worked.

dlb
I'll have to flag this for Nicholas, that was my only idea. :(


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

nicholas
Akeeba Staff
Manager
You are right, there has been a problem with the MultiDB feature of Akeeba Backup Professional 3.0.a1. I have just uploaded an updated package for subscribers to the Professional edition including a fix for this issue. Please download the package to hotfix release 3.0.a1.1 and install it on top of your existing installation. This should allow the MultiDB feature to work properly. Thank you!

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!

user8566
Nicholas, The patch fixed the database connection problem but now I'm getting an error during the backup that I wasn't getting previous to patching:

Couldn't write to the archive file; check the output directory permissions and make sure you have enough disk space available.

I went as far as changing permissions to 777 on my output directory and still the error comes up. Prior to the hot fix, I was able to do a normal backup fine.

nicholas
Akeeba Staff
Manager
The 3.0.a1 had a bug which wouldn't report cases where it couldn't write to the backup file. 3.0.a1.1 addresses this issue and throws an error when it can't write to the archive file. I don't think that your problem is permissions. I think that you are really running out of disk space. Generally, you should not exceed 50% of your server quota limit to take a successful backup with Akeeba Backup, the same restriction there was with JoomlaPack. It simply needs space to store the backup archive.

If you ZIP and attach your backup log file I will be able to tell you exactly what you should do to work around the problem.

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!

user8566
Hi Nicholas,
I can definitely tell you it's not a legitimate disk space error. As I mentioned, before doing this update to fix the database issue, I was able to successfully run a backup and restore it without any problem. Also, I am on an unlimited disk space and bandwidth plan. Here's the zip...let me know what you think. Thanks!

TEXT

nicholas
Akeeba Staff
Manager
Ah! You're right, there is a bug in the split archive support code which throws this error. By default, Akeeba Backup 3.0.a1 creates split archives with a part size of 5Mb. Since you're on unlimited disk space you can go to Configuration, click the "Configure" button next to the Archiver engine selection box and drag the "Part size for split archives" all the way to the left (0.00 Mb). This is a temporary fix; the proper fix will be released tomorrow with 3.0.a2.

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!

user8566
Great job! That quickfix works for me...I was thinking about switching to a single file backup anyway. I didn't test a restore, but I successfully backed up a few sites and external databases and extracted everything successfully with the windows component.

I do have a question though... is there any meaning/reason behind the prefixes that get added to the folder names in the external_files folder? Same thing on the databases...

nicholas
Akeeba Staff
Manager
The prefixes are there to work around a potential problem. Let's say your database is named "joomla" and it's on localhost. You include another database named "joomla", on mysql.someotherhost.com. If there were no prefixes, the dump file of the latter would overwrite the dump file of the former. Same goes for external directories. The unique prefix makes sure that naming clashes would have no consequence.

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: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!

Summer vacations: Our support will be closed for replies and new tickets from August 6th to August 21st, 2022 due to summer vacations.