Support

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:
I upload the backup for my site to Amazon S3. When I use Akeeba Backup 4.3.1, the "Part size for split archives" works 100% when I set it to 100MB. When I upgraded to 4.4.2, I have had to reduce this to all the way down to 5, which means I have 58 files in the backup. I did note that in 4.4.2 a new Amazon S3 engine was included. Is the smaller archive split size a new requirement, or is there a way to allow larger split sizes?

I have reconfirmed the issue is between 4.3.1 and 4.4.2 by checking the backup process at my non-production site.

Thanks!

Thanks, Nicholas. I downloaded the file com_akeeba-rev494AAA8-pro.zip and installed it on my non-production site. The transfer to Amazon S3 is still not working. I receive the following message:

Warnings
Upload cannot be initialised. Amazon S3 returned an error message: 0 :: Akeeba\Engine\Postproc\Connector\S3v4\Connector::startMultipart(): [0] The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'us-west-1' Debug info: SimpleXMLElement Object ( [Code] => AuthorizationHeaderMalformed [Message] => The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'us-west-1' [Region] => us-west-1 [RequestId] => 15E38EEAF362462D [HostId] => oqBOtHwq6YRBPzyEisNtPY/gUuYh654xB9XDqg5cRoWc+m0sFB16ph70rcP2DYNxCT3+Gm3UNIQ= )
Failed to process file /home/silver54/public_html/_SPW_Test/administrator/components/com_akeeba/backup/SWPTEST-silverpen.org-20151019-202335.jpa
Post-processing interrupted -- no more files will be transferred

(I tried to attach the log file but it didn't take)

Here's the log file

Sorry - one more try. I forgot to zip the file.

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.