Support

In order to create a Joomla development site, I used the import Amazon S3 archives method to import the db from my production site (Site A) to a second pre-installed Joomla site (Site B).

When the installation script requested my database credentials, I entered the credentials for Site B.

The restore process seemed to progress as desired until about 80% complete when a server connection issue interrupted the process. Akeeba displayed a popup that sent me back to the beginning of the installation process, but the connection error persisted. With no other way to get out of the installation loop, I was forced to remove the installation script.

Unexpectedly, after that failed restore, Site B ended up being configured with the same database as Site A; both sites are using the same db. Therefore, I don't have an Akeeba log or bug report from that installation attempt to submit.

I'm not sure what went wrong, or if I was using the correct/best method to achieve what I wanted. Please advise.

One of the last things that happens in the restore process is the new configuration.php file for Site B is written out. Since it never completely finished, this didn't happen and it is using the old, Site A configuration.php file.

It makes me a little nervous that the restore didn't finish, but you should be able to tell pretty quickly if the database restore was not complete. You have two options:

• If you have not yet deleted the /installation folder, you can do the restore step again, just visit the Site B URL and you will be redirected into the script. (You do not need to worry about the extraction, that was complete when the problem occurred.)
• You can manually edit Site B's configuration.php file and put in the proper database connection details for the new Site B database.

Dale,

One of the last things that happens in the restore process is the new configuration.php file for Site B is written out. Since it never completely finished, this didn't happen and it is using the old, Site A configuration.php file.

Thank you. That's the piece of the puzzle that was unclear. I was not sure if the config file was to be updated by Akeeba.

I will be editing the db credentials in the config file shortly, however two questions come to mind:

1- If after updating the config file, I find that the restore for Site B's db was not completed, what kind of issues could cause that scenario?

2- If there was an error on my part such as an incorrect password, is it true that Akeeba would have flagged that early on, before starting the restore?

Joann Lyles

Joann,

If you think that the database did not restore completely, start over. It isn't worth it to do work on your dev site only to find the restore was incomplete.

Yes, if the database credentials were incorrect, the restore script would have told you that and given you a chance to correct them.

For future reference, you do not need a working Joomla! site to restore your backup. You can put the backup archive in the root of your target site and use Kickstart (available on our Download page) to extract the archive and start the restore script.

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.