Support

Site Restoration

#35201 Large zip file in archive halts the extraction

Posted in ‘Site restoration’
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

PHP version
n/a
CMS Type
Other
CMS Version
n/a
Backup Tool Version
n/a
Kickstart version
n/a

mattyshigh

Hi there, a large zip file (11 gig) was left on the server during the back-up process by accident and was included in the JPA archive. The back up completed without error and automatically uploaded to dropbox. 

When we come to restore the archive it always chokes (an unexpected error occurred) when we hit the directory containing the mentioned zip file. Is there anyway to remove it from the manifest or indeed to exclude this folder during the extraction process?

I have attached a copy of the debug.txt file. 

Many thanks in advance.  

nicholas
Akeeba Staff
Manager

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!

mattyshigh

Ok, thank you, I really appreciate the response. We will certainly not make that mistake again! 

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!

Summer vacations: Our support will be closed for replies and new tickets from August 6th to August 21st, 2022 due to summer vacations.