Support

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.8
PHP version: 5.3.14
MySQL version: Server version: 5.5.28-0ubuntu0.12.04.3
Host: localhost
Akeeba Backup version which took the backup: 3.6.12 (2013-01-04)
Kickstart version used to extract the backup: (unknown)

Description of my issue:

I have a production version on the server for a website and a development version on my computer (localhost). I am storing akeeba backups in an Amazon S3 bucket.  I made some changes to the live site and wanted to restore (i.e., overwrite) my local version with the live site database and files.  So I chose Import Achives from the Manage Backups screen.  The S3 archive showed up fine on the import screen:

After the import, the message "Import operation completed successfully" was displayed.  However, there were no entries in the backup screen:

And yet the actual backup files that came from S3 were sitting in the backup directory:

So I went back to Import Archives, but this time clicked "Scan for files" and selected the above archive.

Now the archive showed up in the backup/restore list.  However, when I did the restoration, I received this error:

Despite this error, Akeeba proceeded with the restoration.  I did not see any way to abort this process.  It appears like the restoration worked correctly, but it is hard to tell without testing every single page in the site (not reasonable).  So is my development localhost potentially corrupted now due to the above error?  Is there a way to abort the restoration process in situations like this?  But, most importantly, is there a way to avoid the above error when importing an archive from S3 and restoring it?

Sure, renaming to "Download from S3" would help.  And, perhaps a note that if you want to manage the archive, to select "Scan for files" from the backup output directory.  Or, just add the S3 archive to the list of "Managed Backups." :)

So I downloaded the archive directly from AWS console, imported/scanned it into Akeeba and restored.  Everything worked correctly, so this tells me that the archive up on S3 must be okay.

So I deleted the archive from Akeeba and tried to import again from S3 using Akeeba's import option.  I think something is not quite right as it transfers it from S3.  When I click on the archive name in Akeeba, all I see is a spinning circle icon (I'm using Windows 7 for this/localhost -- server is running Ubuntu).  Then, the 100% progress bar appears after some time (presumably downloading):

But notice it is over 100% and... it just keeps going:

until it has downloaded almost twice the size of the archive and get the success message:

This is what I downloaded directly from S3 via AWS console:

This is what Akeeba downloaded from S3:

So I guess this is why the import failed originally--the download process from S3 via Akeeba is not quite correct, or at least not what was expected?

But I have a accurate restore now on the local system, so that's good!  The ability to download from S3 directly in Akeeba is a really nice feature, though, and would rather do that download directly in Akeeba rather than go through the AWS console.