I see a different problem in the log file. It seems to be an issue with the backup integrity. The file media/com_easysocial/photos.zip seems to have not been backed up correctly. You said it's 11GB which is the reason. Files over 2GB minus one byte fail to back up on 32-bit versions of PHP due to the way PHP handles file size internally. That's why your backup size is 2.1GB even though there should've been an 11GB file in it. PHP reported the file as fully read at around 900MB.
Her's the problem. The resulting backup archive is now corrupt because the nominal end of the backed up file (start of its data + its reported length of 11GB) does not coincide with the actual end of the file's data in the archive (start of its data + 900MB actually read before PHP said the file is fully read). Kickstart tries to do some heuristics to find the next file but it fails. Hence the weird, scrambled file name you see in the next log line and the failure to extract the archive.
You would need to take a new backup without this big file included.
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!
