Support

If you are talking about the quota size limit there's a reason it's limited to 4GB minus 1 byte: that's the maximum integer you can express with 32–bit integer values, a limitation of certain versions of PHP. When you go past that PHP starts using floats which incur a loss of precision.

That said, the value chose was actually a bug. The maximum integer PHP supports is 2GB minus one byte. Considering that nobody has run into a problem even though quotas over 2GB may be turned into floats I think it's safe to increase the upper limit of quotas to 1 Petabyte — that's more than what you are likely to ever use, typically disk quotas are in the two digit Gigabytes.

I will not change the part size for split archives, though. When we are extracting a backup archive we need to deterministically use bytes even on the 32–bit Windows builds which are extremely common with prepackaged local server environments such as WAMPserver, XAMPP etc. The only way to guarantee that is to keep the part size under 2Gb minus one byte. Anything over that and you will be unable to extract backup archives on Windows because the file offset is converted to a float which is not precise enough for byte–aligned file reading.

Yes. I already made the change to 1Pb (1024Tb). This change will be included in the next official release, scheduled for late September to early October.