Support

Akeeba Backup for Joomla!

#8378 eXtract Wizard Not Extracting Everything

Posted in ‘Akeeba Backup for Joomla!’
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
n/a
PHP version
n/a
Akeeba Backup version
n/a

user8566
I'm working with an archive containing many websites backed up using the external directory feature. I successfully backed up over 5GB of data and downloaded via FTP. I have my configuration set to divide the JPA into 500mb portions, so in total I have 11 archive files. (1 .jpa and a bunch of numbered .j01, .j02, etc)

My problem is when I ran the extractor on my local machine to ensure the archive could be opened and examine the data, only about 1.5gb of data was extracted yet no errors were detected (i unchecked the box about ignoring errors). When examining the external_files folder, there are only 10 of my external site folders. There should be MANY more, and these other missing folders ARE referenced in the README.txt file that is generated.

Any ideas? Thanks in advance!

dlb
I'll flag this for Nicholas to look at.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

nicholas
Akeeba Staff
Manager
eXtract Wizard shouldn't have a problem with very large archives, as it internally uses 64-bit pointers. Do you see the progress bar filling up, or it just stucks at a specific point and won't go any further?

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!

user8566
The progress bar goes across slowly as it processes the various files... then it hits a point and goes very fast through a few files all the way to the end and reports as a successful extraction.

I need to be able to download and extract locally. If we can't figure this one out I'm not against using Zip format, but I just tried that and hit a whole different issue there. I'd much rather prefer figuring out this JPA extraction if possible.

nicholas
Akeeba Staff
Manager
What you describe is pretty much a normal run. The slow part in the beginning? This is extracting the database dump, which is one big file. The fast roll at the end troubles me. It usually means that there are some files which can't be extracted on Windows, e.g. files having \ or : in their name. I would really like to see the backup log of this archive. I think that the problem is not in the extraction phase after all.

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!

user8566
I don't have the log on that particular backup any longer. I ran another one last night with smaller 100mb chunks and I'm downloading those via FTP right now. I'll save the log from this time and let you know if the same problem happens. Thanks.

user8566
Same result after trying to extract the backup made with smaller chunks. I watched a little closer this time though and one thing to note...It actually did not jump all the way to 100% as I had thought. The bar filled up to about 3/4 of the way and the completion message popped up. If it did jump to full, it happened so quickly I could not see it.

Nicholas - keep an eye out in your email. I'll send you a link to download the log, it's a big file.

nicholas
Akeeba Staff
Manager
Sounds like a corrupt backup file. Please send in the log.

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!

user8566
I tried to attach the log as a zip and it told me the file is too big. I emailed yesterday to your MSN addresses listed as your MSN messenger ID in your profile though.

nicholas
Akeeba Staff
Manager
The message never got through and I can't seem to locate it in the spam inbox. As this Hotmail account is only used for MSN, please email the log again at nicholas at akeebabackup dot com. Thanks!

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!

nicholas
Akeeba Staff
Manager
Dave,

I just received your logs. There are several things regarding what you're trying to do here.

First thing, the way you are trying to use the external directories inclusion is counter-effective and unsupported. You are trying to backup multiple Joomla! web sites by using the external directories and extra databases definitions. However, when you try to restore this backup, you will have to do so manual, as ABI is only able to update a single configuration.php file, namely the one from the main website (the one where the backup was launched from). It's best to setup one backup run for each site you want to backup. After all, there is no domain installation limit for Akeeba Backup.

The second thing I have to warn you about is that you seem to be running the backup on a 32-bit server. Unfortunately, PHP has an inherent limitation. On 32-bit systems it can only be used to reliably create files up to 2Gb in size. Anything over that and all bets are off. On the other hand, on 64-bit systems the maximum file size is in the range of several petabytes, which is practically unlimited by today's standards. If you try to create a backup archive over 2Gb on 32-bit PHP, the internal file pointers get corrupt on files around the 2Gb boundary and any extraction software (including Akeeba eXtract Wizard) will choke on them somewhere near this 2Gb limit.

I suggest that you install Akeeba Backup on each of your sites and create a backup profile for each of them. You can then either use a CRON job to back them all up, or use Akeeba Remote Control for a single-click solution to backing up and downloading the backup archives of all of your sites - or even scheduling this! - from your local PC.

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!

user8566
Hi Nicholas,

Thanks for the info. I understand that the restore would have been a manual process by backing up many sites with one site being my "main" one and utilizing external directories for the other...I just loved the thought of a "one click backup solution" rather than setting up many scheduled jobs. I'll take your advice though and look into Schedule This or back to cron jobs.

With all that said, I'll consider this a closed issue... I just want to remind you that I did have my backups set to as small as 100mb chunks and still had the issue of not being able to extract. While the overall setup is unsupported from a restoration standpoint, from what you're saying it still should have extracted by keeping the archive sizes to relatively small pieces. Just something to keep in the back of your mind just in case another user down the road has a similar issue...we never really pinpointed why it exactly stopped at 10 external directories.

I'll definitely continue to use the product just for the fact that i can still back up many databases with a single click though...that in itself still makes this product an invaluable tool! Thanks again for the great support!

nicholas
Akeeba Staff
Manager
When you say "100Mb chunks" are you referring to split archives or small backup jobs of 100Mb each?

If it's the former, I will have to repeat that the issue is the total size of the backup set, not the size of the individual part. When the total size of the backup set reached 2Gb, all bets are off. This is a PHP limitation we can't overcome. The only workaround is switching to a 64-bit machine running the 64-bit version of PHP.

If it's the latter, it surely is a file corrupt during transfer. Do note that using your browser to download the backup archives - i.e. using the Download button in Administer Backup Files - may not be the best idea in the world. You must download the files through FTP in BINARY transfer mode. Do NOT ignore this last bit!! Most FTP clients work in AUTO mode which will resort to ASCII transfer for unknown file types. This usually means that backup archives get to be transferred in ASCII mode, which screws them up. You MUST use the BINARY transfer mode; in FileZilla it's a matter of clicking the Transfer, Transfer Type menu and make sure Binary is checked. Alternatively, use Remote Control to perform the file transfer (it internally uses FTP in BINARY mode); right-click on a site definition and click on manage backups. This will allow you to pick and download the files of any backup set on your server.

I am pretty sure we can make this work for you in order to provide a complete full site backup solution.

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!

user8566
I was referring to split archives... If the full backup can't be over 2gb, even with splitting the archive, that's definitely my problem. Maybe I can get this to work by being a little more picky about which directories to backup and exclude a few huge things that don't have to get backed up every time. I did use Cuteftp in forced binary mode once to make sure that wasn't the issue so you're probably dead on with the 32 bit limitation. Thanks 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.