We are having the same issue as described in https://www.akeeba.com/support/akeeba-solo/37607-transfer-to-azure-gives-connector-not-found.html only we are are using Akeeba Backup Pro.
Can you apply the same fixed to an Akeeba Backup Pro dev version?
#37732 Azure Blog Post Processing Issue
Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket
Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Environment Information
Joomla! version
3.10.11
PHP version
7.4.x
Akeeba Backup version
8.1.10
Latest post by ibweb on Wednesday, 14 September 2022 08:14 CDT
Tuesday, 13 September 2022 00:24 CDT
nicholas
Akeeba Staff
Manager
Yes, indeed! The problem is in the backup engine code which is common between all our backup software (Akeeba Engine). I did apply the updated code, thus the fix, to Akeeba Backup Professional 8.x as well. You can find the dev release at https://www.akeeba.com/download/akeebapro/8-2-0-dev202209130521-rev26931379.html
Please let me know if the fix works for you. As you saw in the other ticket I couldn't get a reply yet since the other client just became father for the third time. I am waiting on someone outside the company confirming the fix on their real world site before making a new release.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Tuesday, 13 September 2022 13:12 CDT
ibweb
The fix worked. After upgrading to the dev version, we ran a test backup - success.
We also re-pushed the backups that had failed to push over to Azure via Akeeba - now those went through successfully as well.
On a side note, we have multiple sites that push automated backups to Azure. We only had 1 that experienced this issue, which is now resolved.
Wednesday, 14 September 2022 00:05 CDT
nicholas
Akeeba Staff
Manager
It was a tricky issue. It would only happen if you had a multi-part backup archive where the last part happened to be smaller than the Azure upload chunk size (by default: 10MB). That's why only you and Carlos ran into it on one site each: the chances of that happening are very low but thanks to the Law of Truly Large Numbers we get bug reports even for the most unlikely of issues within a week of the release where the bug first appears.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Wednesday, 14 September 2022 08:14 CDT
ibweb
Ahh, that is certainly a unique issue. Thanks for the clarification.
Feel free to close out this ticket at will.