Jeremy Davis's picture

Deep apologies on the radio silence. I have been madly trying to push v14.1 out the door and as always these things take longer than I think it should...

Anyway, I am not at all sure about what the issue is and TBH am surprised that using the limits didn't work around it. It makes me wonder if the file in question is actually missing from your backup and that's what is causing the issue?

Looking at the path; it is possible that you could actually exclude that cache location anyway. Most webapps do not need their cache backedup as it can be reproduced. It may be worth trying to exclude the /var/www/shop.public_html/var/cache/ path from your backup.

Assuming that this is testing, then perhaps it's worth doing a new clean full backup (with the cache excluded) and trying the restore again? Obviously if you are trying to restore because you need the backup then that is a different matter. I suggest that you try downloading the backup first using the --raw-download switch, then try restoring the downloaded files. Like this:

tklbam-restore 1 --raw-download=/tmp/mybackup
tklbam-restore /tmp/mybackup

Also you mention in your first post that you ran out of room. You do need a fair bit of space. Essentially it downloads the compressed backup; it then extracts the archive; it then copies it across keeping track of any overwritten files (so they can be restored if you choose to rollback).