How to increase archive file system limit

We have removed the limit in the beta Version if only present there if you use a 32 Bit PHP Version.
https://github.com/inpsyde/backwpup

Hi Daniel. How do you configure the github version of the plugin to ignore the 2GB file size limit? I’ve installed the github version, activated version 3.2.0-rc1, but I can’t see that setting anywhere in the UI. I searched the source code and the only place I can see “2GB” is in the release notes.

When I use the released version I get things like this in the logs

ERROR: If /home/username/public_html/wp-content/uploads/2015/06/15-9616-post/imagename_(pp_w1136_h756).jpg will be added to your backup archive, the archive will be too large for many file systems (over 2GB). You might want to consider splitting the backup job in multiple jobs with less files each.

The backup is for a photographers blog with 10GB of images.

I’ve tried the github version of the plugin on two different blogs, on two different servers, both Intel 64 running unix. The second is the one I’m really interested in.

Linux xxxx.hostgator.com 3.12.35.1418868451 #1 SMP Wed Dec 17 20:10:32 CST 2014 x86_64

Linux xxxx.hosting-services.net.au 2.6.32-531.23.3.lve1.3.6.el6.x86_64 #1 SMP Mon Sep 29 16:27:54 CEST 2014 x86_64

More info about the second server
– PHP 5.5.29
– Server LiteSpeed
– OS Linux
– PHp Memory Limit 256M

Pleas have a look that you have a 64Bit PHP Version. You can see this in the first lines of the log file.
BackWPup > Settings > Tab Log thre must be debug Log enabled.

You can use a 32Bit PHP Version on a 64Bit Server!

Thanks Daniel.

[INFO] BackWPup version 3.1.4; A project of Inpsyde GmbH
[INFO] WordPress version 4.3
[INFO] BackWPup job: WordPress Media Backups 2015 and later; FILE
[INFO] BackWPup cron: 0 3 1 * *; Next: Thu, 1 Oct 2015 @ 03:00
[INFO] BackWPup job started manually
[INFO] PHP ver.: 5.5.29 (64bit); litespeed; Linux

So you can’t have files above 2GB with a 64bit PHP version? That seems backwards, 64 bit should have >2GB support natively.

It’s generally impossible to change the PHP version on shared hosting. Interested to hear more about this limitation and how it could be worked around.

Oh i think you have the version form github. on Version 3.1.4 you can’t use archves lager than 2 GB with this https://github.com/inpsyde/backwpup/releases/download/3.2.0-rc1/backwpup-3.2.0-rc1.zip version you can use bigger archives again.

Sorry, I posted the wrong log earlier. I manage about ten blogs and I’m actively working on three of them today, I got mixed up.

Here’s the information about the right blog below. Now I have the 3.2.0-RC1 version should it automatically go over 2GB files? I just can’t find any option to let it go over 2GB that I saw mentioned somewhere.

[INFO] BackWPup 3.2.0-rc1; A project of Inpsyde GmbH
[INFO] WordPress 4.3.1 on (removed)
[INFO] BackWPup job: Weekly WordPress Database Backup; DBDUMP+WPEXP
[INFO] Runs with user:
[INFO] Cron: 0 3 * * 0; Next: Sun, 20 Sep 2015 @ 03:00
[INFO] BackWPup job started manually
[INFO] PHP ver.: 5.5.29 (64bit); litespeed; Linux
[INFO] curl ver.: 7.38.0; OpenSSL/1.0.1e

Yes, it goes autmaticly over 2GB! Did it work ?

Yes, it did, thanks!

One thing I find quite regularly is 500 errors communicating with dropbox, far more often than I’d expect. Could you implement a silent retry mechanism before putting errors in log and emailing people with those errors?