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: Automatic Backup does not completely upload all the files to s3 bucket. This problem is not usually seen while a manual backup is triggered. We have been using akeeba backup for quite sometime now but now problems have started lately. It would be really helpfull if the cause of issue is found and gets fixed.

This is much more serious than a failure to upload to S3, this backup did not complete.

How was the backup started? Is this from the back end or a CRON job? If a CRON job, is is a front end backup or a command line?

Do you see any error message when the backup quits?

Akeeba was updated yesterday, now the version is 'Akeeba Backup Professional 5.2.2 (2016-09-13)'

The automatic backups are started using this command:

curl -L --max-redirs 1000 -v "http://dev25.educase.com/index.php?option=com_akeeba&view=backup&key=XXXXXXXXX" 1>

Still we have this problem where not all .jxx files are uploaded to the bucket.

Today while trying a manual backup, we got this message:

0 :: Akeeba\Engine\Postproc\Connector\S3v4\Connector::putObject(): [56] Recv failure: Connection reset by peer Debug info:
Failed to process file /server_path/com_akeeba/backup/site-dev25.educase.com-20160914-125041.j07
Post-processing interrupted -- no more files will be transferred

Also we received these warning messages:

'Column xxx of table #__xxx contains 1195567 bytes of data. This may cause restoration issues.'

Wondering whether this could hamper successful restoration..

Akeeba was updated yesterday, now the version is 'Akeeba Backup Professional 5.2.2 (2016-09-13)'

The automatic backups are started using this command:

curl -L --max-redirs 1000 -v "http://dev25.educase.com/index.php?option=com_akeeba&view=backup&key=XXXXXXXXX" 1>

Still we have this problem where not all .jxx files are uploaded to the bucket.

Today while trying a manual backup, we got this message:

0 :: Akeeba\Engine\Postproc\Connector\S3v4\Connector::putObject(): [56] Recv failure: Connection reset by peer Debug info:
Failed to process file /server_path/com_akeeba/backup/site-dev25.educase.com-20160914-125041.j07
Post-processing interrupted -- no more files will be transferred

Also we received these warning messages:

'Column xxx of table #__xxx contains 1195567 bytes of data. This may cause restoration issues.'

Wondering whether this could hamper successful restoration..

The "Connection reset by peer" message means that S3 broke the connection on their end. This is usually a momentary error, their server is too busy perhaps. There isn't anything that we can do on our end to prevent it.

The column message is a new warning. Nicholas gave me this information for another ticket:

As long as their target server has a high enough MySQL maximum packet size they can ignore this warning. If they get restoration errors they should read this warning again and set the max packet size higher because that's a MySQL limitation.

Also in general large columns are not a brilliant idea anyway

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.