So far, every time we saw this issue, it was caused by the hosting company.
Some of them will rename Akeeba Backup files because they found "suspicious" words inside them, like pack or symlink.
As you can easily image, renaming (or even worse deleting) files will lead to fatal errors, this is why your log interrupts after few lines.
Can you please run a kick check in the administrator/components/com_akeeba/akeeba folder and subfolders, looking for a file that contains a number? Something like foobar.1.php.
Usually the hosting company renames them using this pattern.
If you can't find any renamed file, most likely it was deleted, this means that you have to confront your remote installation with a fresh downloaded package.
Usually the hosting company will touch the files under the folder I wrote above.
If you can confirm this is your scenario, the only solution is to change your hosting company or ask them to stop this kind of actions.
Knowing the name of your hosting company will speed up the test, since we maintain a list of such companies.
Davide Tampellini
Developer and Support Staff
🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!