Support

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!

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.

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

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

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.

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

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...