Support

Site Restoration

#12652 How to extract some files from a backup file

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

Latest post by nicholas on Saturday, 16 June 2012 03:00 CDT

user63906
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? No
Have I searched the tickets before posting? No
Have I read the documentation before posting (which pages?)? No
Joomla! version: (1.5.23)
PHP version: (5.3.6)
MySQL version: (unknown)
Host: (Linux)
Akeeba Backup version which took the backup: (3.0.b2 (2010-04-27))
Kickstart version used to extract the backup: (kickstart-pro-3.5.1)

Description of my issue:

Hello,
I need to extract only the image directory and everything beneath it, because by mistake I deleted it.
Please let me know how use KickStart, not for restoring the complete site, but only one Directory and its content.
Just for you to know, the backup .jpa file is already on the target server, in the same place where the backup was taken (/home/myUserId/public_html/administrator/components/com_akeeba/backup).
Thanks a lot
Saverio

nicholas
Akeeba Staff
Manager
You have to download the backup archive to your local PC, using FTP in binary trasnfer mode, first. Then use Akeeba eXtract Wizard to extract the archive. You can now upload any files you want.

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!

user63906

user63906
Thanks Nicholas,
Your advice is very clear, however, I was wondering if are there other options, as it is going to take forever to download a 7.2 Gb backup file to my PC.
Thanks again
Saverio

nicholas
Akeeba Staff
Manager
The other possibility is to use Kickstart (or Akeeba Backup itself) to extract the backup archive. Then, instead of going through with the restoration, delete the installation directory. However, I advise against that method unless you know what you're doing. If you restore a backup archive on top of a site with updated versions of components you may break your site. The safe method is local extraction.

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!

user63906
Hi Nicholas,
Not so good news.
a) I downloaded my jpa backup file (7Gb). The size of the downloaded file matches the size of the backup file, and FileZilla did not show any errors.
b) I used the latest Akeeba Extract (3.3) for Windows.
c) The extracting process took only a minute or two, and got a "Your archive was successfully extracted" message, but, the extracted directory shows only two directories and 30 or so files, instead of, like a thousand or more files, directories, data bases, etc.
d) I run the program with the check box "Ignore most errors" unchecked.
e) The Dry Run test gave me the same "successfully extracted" message.
f) I tried to download the file with fireFTP, but it only supports files up to 4Gb. Also tried to download the file with the firefox buil in ftp, but aborted after a while.
g) Maybe if I could split the file in small segments.


Appreciate your kind comments
Thanks
Saverio

nicholas
Akeeba Staff
Manager
I just realised you are using Akeeba Backup 3.0.b2 which is more than 2 years old, not supported and has known issues. Sorry, your backups seem to be genuinely corrupt because that version was buggy. That's why I had released an updated version back then. For the record, there are almost three dozen releases between your version and the last supported version on Joomla! 1.5, Akeeba Backup 3.4.3. Unfortunately, I can't help you: the backup is corrupt and I know why. There was an error log file or another file which kept growing while the backup was in progress. This ancient, outdated, buggy version of Akeeba Backup had a problem with such files which would corrupt the backu archive.

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!

user63906
Oh!this is really a very, very bad news.
Hope Akeeba will immediately notify the V3.4.3 users, should they find a bug that ruins the files.
Anyway it is my fault, because I should test the recovery in the first place, before using the product.
Hope 3.4.3 is stable.
Thanks Nicholas and regards
Saverio

nicholas
Akeeba Staff
Manager
Well, I've always been publishing release announcements which let you know of the bug fixes in newer releases. Two years ago, Akeeba Backup 3.0's alphas and betas were really unstable. I was in the process of rewriting the JoomlaPack component into something completely new, with a modern engine and a new UI. Bugs were routinely found and fixed. I would say that ever since version 3.2.x Akeeba Backup is a very robust component which doesn't corrupt backup archives, at least not without throwing an error or warning.

As for version 3.4.3, it's rock solid. That's why I chose it as the final version for Joomla! 1.5; I would never choose a final version with grave issues, it would be irresponsible. There are only a few minor cosmetic issues and a minor bug which don't affect backup validity. These issues are so unimportant that they wouldn't warrant a new release anyway.

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!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

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!