Support

The screenshot never came through, but I suspect you are talking about the database restoration step. Which version of Akeeba Backup was used to take that backup? If it was before 3.1.1 you will have to adjust some options in the Fine Tuning section of the restoration script to make it work. It would also help me knowing if you are using Windows and which version (XP, Vista, 7) :)

As I told you in my last two emails, the username you used to register for the Pro subscription is BarnQueen21. Please login using that username, then proceed to Downloads. Click on Akeeba Backup. A list of version appears. Click on Akeeba Backup 3.1.2. Look two boxes down for the "Akeeba Backup Professional" title. Click on it. The component downloads ;)

Regarding your other issue, when you reach the database restoration page and after entering your new (local) server's connection details but before clicking on the "Next" button, click on the Fine Tuning pane header towards the bottom of the page. In there you will find some options. You need to change the maximum size to process at once to 131072 and the max number of SQL statements to 20. This will slow down the restoration a little bit, but it should not throw timeout errors any more.

However, if you take a new backup of the site using Akeeba Backup 3.1.2 and try to restore that backup, none of this is necessary. We have updated the integrated installer to intelligently avoid timeout errors even on the (very slow) Windows environment :)

I was assuming you were using the correct database connection information without making sure that this was the case. I apologize. What happens is that if you give the wrong hostname or port then PHP may hang forever trying to connect to the out-of-reach host. This causes a non-catchable timeout error. Unfortunately, AFAIK, this is a limitation of PHP which I would only wish I was able to work around :(

Kate,

If you get a timeout after setting the maximum execution time to 99999 seconds, you have a terrible lot of patience (99999 seconds is one day and three hours), you are editing the wrong php.ini or you simply forgot to restart Apache. I suspect the latter two. So, before doing anything else, make sure you're editing the correct php.ini -note that there is one for mod_php, one for CGI and one for CLI- and restart Apache to activate the change. Visiting a page which only runs phpinfo() would allow you to ensure your changes are actually propagated to the server.

That said, there are two database connection options, mysql and mysqli (with an i at the end). Most Joomla! 1.5 sites need the former, without the trailing i. Try using each one alternatively in order to find out which one works on your server. If one gives a timeout, the other one will work.

Then check your database host name. It's not always localhost. Some hosts use an IP address (e.g. 1.2.3.4) others use a full domain name (i.e. mysql.myhost.com). If in doubt, please ask whoever manages your server. Pitfall: This has happened to yours truly. On a server I manage, there is no support for named pipes built in MySQL, which means that "localhost" never works. When I tried 127.0.0.1 it worked. Why? Because 127.0.0.1 tells PHP to use TCP/IP networking to connect to MySQL whereas "localhost" tells it to use named pipes.

Check your database name. Hosts based on cPanel and Plesk prefix the datbase name with your account name. For example, if your user account name on the host's server is "foo" and you try to create a database named "bar" the real database name is "foo_bar", not just "bar"! Do note that this prefix has nothing to do with the table name prefix (e.g. jos_) used by Joomla!. If in doubt, ask whoever set up your server.

Check your username. The same principles with the database name apply, i.e. those hosts will prefix the database username with your account's name.

Finally, if you had created your backup archive with Akeeba Backup 3.0.x or if you are unsure about the version of Akeeba Backup which created the archive, please try using a database password which consists only of unaccented alphanumeric characters (a-z, A-Z and 0-9).

If all else fails, you can find the dine tuning parameters in the "Restore DB" step page, where you supply the new database connection details. Just click on the "Fine Tuning" header towards the bottom of the page to open them. Depending on the Akeeba Backup version you were using to create the archive you will either find the parameters you mentioned (Akeeba Backup 3.1.5 and earlier releases) or a maximum execution time parameter (Akeeba Backup 3.2.b1 and later releases).

After all that long explanation it's time for me to suggest a quick fix. I am not a gambling man, but if I had to take a bet on the most possible culprit, I'd say that either you're using the wrong database connection type (mysql vs. mysqli) or the wrong hostname (localhost vs. 127.0.0.1).