UNiTE, Remote CLI, eXtract Wizard

Saturday, 13 December 2008 15:20 CST

user1681

Problem Description:

Once the backup file is administrated to my desktop, I attempt to use the Joomla Pack eXtract Wizard to unzip the .jpa file (The file is 2.0 GB). After I choose the file and the extraction destination and click on next I receive an error saying

\"TProgressBar property out of range.\"

It renders this error regardless of where I extract the files. Any suggestions would be appreciated

Log/Error Message:

TProgressBar property out of range.

Diagnostic Information

Joomla! Version: Joomla! 1.5.8 Production/Stable [ Wohnaiki ] 10-November-2008 23:00 GMT

configuration.php: Writable (Mode: 755 ) | RG_EMULATION: N/A

Architecture/Platform: Linux 2.6.27 ( i686) | Web Server: Apache/2.2.10 (Unix) mod_ssl/2.2.10 OpenSSL/0.9.8i DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 ( http://www.ourfamilypetstore.com ) | PHP Version: 5.2.6

PHP Requirements: register_globals: Disabled | magic_quotes_gpc: Enabled | safe_mode: Disabled | MySQL Support: Yes | XML Support: Yes | zlib Support: Yes

mbstring Support (1.5): Yes | iconv Support (1.5): Yes | save.session_path: Writable | Max.Execution Time: 30 seconds | File Uploads: Enabled

MySQL Version: 5.0.51a-community ( Localhost via UNIX socket )

Extended Information:

SEF: Disabled (without ReWrite) | FTP Layer: Enabled | htaccess: Implemented

PHP/suExec: User and Web Server accounts are the same. (PHP/suExec probably installed)

PHP Environment: API: cgi | MySQLi: Yes | Max. Memory: 64M | Max. Upload Size: 64M | Max. Post Size: 64M | Max. Input Time: 60 | Zend Version: 2.2.0

Disabled Functions: dl

MySQL Client: 5.0.51a ( latin1 )

Saturday, 13 December 2008 21:18 CST

nicholas

I will have to resolve this in a later version. Clearly, a 2Gb+ site was not in this version's design specifications :) In fact, 2Gb is the signed integer limit on 32-bit machines, so I'll have to invent a workaround.

Thank you for your bug report!

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!

Sunday, 14 December 2008 06:21 CST

user1681

Thank you for the speedy response. As a follow up,
is it possible for me to backup my site with Joomla Pack? How would I restore a backup of my directory as well as my SQL? Will it have to be in the zip format?

Thanks again!

Sunday, 14 December 2008 08:40 CST

nicholas

In fact it's JoomlaPack which is backing up your site; Remote is just... a remote front-end for JoomlaPack installed on your site :)

- Using JoomlaPack, backup your site (ZIP or JPA format, it doesn't matter, though JPA is more speedy and space-saving than ZIP).
- Using FTP, download the archive and store it somewhere safe. You could also use the Backup Files Administration page to download it, but it's not a good idea to do so with something as big as a 2Gb backup archive!
- When the need arises, upload the backup archive along with kickstart.php (from the Kickstart package) into the target site. The target site could even be located on a different host (migrating your site) or on the same host as the original (restoring).
- You then visit the Kickstart URL in your browser, which should look something like http://www.example.com/kickstart.php , if your target site is located at http://www.example.com/
- Follow the on-screen instructions. Tip: it's best to use the FTP mode when restoring over an old copy of your site.
- When it finishes up extracting the archive, you click on the first "here" link. This launches JPI3 (the restoration script) in a new window. KEEP BOTH WINDOWS OPEN!
- Follow the instructions of JPI3. Tip: you should probably want to change the database connection information if you're migrating your site.
- When done restoring, close the JPI3 window.
- Back on the Kickstart window, click the second "here" link. This removes the installation directory, the backup archive and kickstart.php itself.
- You are done. Your site is restored/migrated.

If you practice this procedure a couple of times on a local testing host you should be able to restore a site in a matter of minutes. Minus the upload and extraction times, it takes me less than 2 minutes to restore a site. Not bad, huh?

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!

Sunday, 01 November 2009 02:21 CST

user7505

Hi, could you pls let us know roughly when are you able to solve the problem of size limit 2gb?

my website was hacked and i desperately need.
made backup of the website but did not know about the limit, so i got the zipped file and cant do anything about it.

pls help me.

thanks
Nickjp

Sunday, 01 November 2009 15:09 CST

dlb

The 2 Gb limit is a "fuzzy" limit. At that point an internal integer field overflows and has to change to a floating point number. It is supposed to happen automatically. We tend to view any backup file over 2 Gb as questionable. It is way down deep in the php language and it isn't a hard limit. Just because your backup is over 2 Gb doesn't guarantee it is bad.

You can use JoomlaPack 2.3's split archive function to produce a multi-part archive where the individual parts are less than 2 Gb. This solves the problem.

What problem are you getting with your archive file? The zip format is known to produce "invalid" files with certain versions and configurations of php. The most common zip error is a corrupt file, but the file is fine, it is the internal CRC32 checksum that is bad. Try the eXtract program in the Native Tools collection on our downloads page to extract the archive locally. That will tell us if it is simply a CRC32 problem. If it is, we're in good shape.

Dale L. Brackin
Support Specialist

English: 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)

Sunday, 01 November 2009 21:30 CST

nicholas

The 2Gb limit is a "hard limit" imposed by the way PHP works on 32-bit systems. If your host runs the 64-bit version of PHP, the maximum theoretical size limit is almost 70 million Terrabytes, so you needn't worry for the next 50-60 years :) Just ask them if they do run the 64-bit version.

If you want to backup a site more than 2Gb in size on 32-bit PHP installations, there is a workaround. Just use the JPA format and set a fragment size for split files of about 262144000 (250Mb).

Extracting them, that's a different story. Kickstart may or may not be able to handle the task. I would bet against it, if I was a gambling man. However, eXtract from Native Tools will most certainly work.

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