Support

We have been asked by a new client to move their site to our hosting account so that we may take over development. The relationship between this site owner and original developer has degraded to the point of distrust. We do not have ftp access nor have we been given access to PHPMyAdmin (or whatever he has). A core copy of Akeeba had been installed on the site already so we uploaded the professional version. We took a fresh back up and tried to restore and was not successful, it gets about 75% of the way done and hangs. We have tried five times. To get around not downloading directly from the server we have uploaded the backup to S3. After the third attempt we broke it into several chucks (6 parts ). It is a large Joomla site but not Magento large (around 600mb if I recall). The new hosting account has 4gb so plenty of space there - no idea of the current hosting account size though.
I thought perhaps there was a misconfig in the file or db table exclusions so I poked around there. The files exclusion looked just fine, however there were no db tables listed for db table exlcusions. We've done this quite a few times at this point, no expert but certainly not a noob, never seen this before. Any ideas?

That is not what you're supposed to see on the table exclusion page. Akeeba picks up the database connection information from Joomla!, so if your site works, Akeeba should work. This could be explained by a bad upgrade from Core to Pro. The Core version does not have that option. Please install the Pro version twice, back to back, without doing anything else in between. This trick usually works around a glitch in the Joomla! installer where it fails to copy all of the files during an installation or upgrade.

On your extraction issue, will the archive extract on your local computer with the eXtract Wizard (available on our Downloads page)? That gives us an idea if the archive itself is good or not.

In Backup, under Configuration, check the option to Test Archive Integrity. That does a test extract of your archive at the very end of the backup process. Also make sure that Exclude error logs and Exclude host-specific stats folders are both checked. The log files can corrupt the archive if they change size while they are being backed up. The host folders usually can't be restored due to permissions issues.

Thank you for getting back to me. I tried reinstalling twice like you had suggested but that had no effect, the db tables were still not showing.
I did find that there were several joomla sites in different folders (not sure what for) so I selected to disclude them from the backup, took new backups,and moved them over to the new hosting account. This new kickstart worked and I am having the client look through the site to ensure nothing is missing from the folders we discluded.
The copy on our hosting displays the db tables as it should.
Thank you so much for the help - I was able to ascertain that the backup was extract-able by using the extract tool - I appreciate that advice.

Are the table exclusions displaying properly on the new host? Do we need to pursue this farther?

They are displaying properly on the new host. I think all is well on the new hosting account so I think we can officially close this. I think there is just something very wrong with the setup on the old site.

OK, sounds good.

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.