[GH-ISSUE #151] Backups lager than 2GB cannot be restored. #119

Closed
opened 2026-02-27 08:14:26 +03:00 by kerem · 3 comments
Owner

Originally created by @Wodel on GitHub (Oct 13, 2020).
Original GitHub issue: https://github.com/lucascbeyeler/zmbackup/issues/151

Originally assigned to: @lucascbeyeler on GitHub.

ISSUE TYPE
  • Bug Report
ENVIRONMENT VERSION
  • Zmbackup Version: 1.2.3
  • Zimbra Version: 8.8.15 patch 14
  • Linux Distribution & Version: CentOS 7
SUMMARY

Backups lager than 2GB cannot be restored.
I am getting this error message : Error message below:/usr/lib/python2.7/site-packages/urllib3/connectionpool.py:769:

STEPS TO REPRODUCE
Restore a backup of 2.7GB
zmbackup -r -ro full-20200301010607 user@example.com   user-restore@example.com
Error : Error message below:/usr/lib/python2.7/site-packages/urllib3/connectionpool.py:769

Restore a backup of 1.9GB
zmbackup -r -ro full-20200401010607 user@example.com   user-restore@example.com
it works
ACTUAL RESULTS
I tried with other backups 3GB and 800MB and the same results : 
- Larger than 2GB : Error
- Lesser than 2GB : Works

I used strace, and I found that there is an overflowerror : read(3, "\nhttp: error: overflowerror: str"
Reading about httpie, it seems it does not support uploading files larger than 2GB.
The latest version of htpie 2.2.0 does not have support for lager files, this feature is meant to be available on httpie 2.3 which is in dev for now.
Since zmbackup is a bunch of bash scripts, could we use another tool other than httpie to upload larger files?
Originally created by @Wodel on GitHub (Oct 13, 2020). Original GitHub issue: https://github.com/lucascbeyeler/zmbackup/issues/151 Originally assigned to: @lucascbeyeler on GitHub. <!-- Before open an issue, please remember to check our Google Group (link in README.md) and the other issues. Maybe what you want is already answered. You don't need to answer all the questions below, just answer what is pertinent to what you want (You don't need to explain the steps to reproduce and the results if your issue is about the documentation) --> <!-- ISSUE TYPE: Inform what kind of issue we are talking about. Choose only one option. --> ##### ISSUE TYPE - Bug Report <!-- ENVIRONMENT VERSION: Describe the environment you are using the Zmbackup and its version. --> ##### ENVIRONMENT VERSION - Zmbackup Version: 1.2.3 - Zimbra Version: 8.8.15 patch 14 - Linux Distribution & Version: CentOS 7 <!-- SUMMARY: Describe your issue in this field. The more detailed you gave us, more easy and fast will be for us to debug and fix the software. --> ##### SUMMARY Backups lager than 2GB cannot be restored. I am getting this error message : Error message below:/usr/lib/python2.7/site-packages/urllib3/connectionpool.py:769: <!--- SUMMARY:For bugs, show exactly how to reproduce the problem, using a minimal test-case. For new features, show how the feature would be used. --> ##### STEPS TO REPRODUCE ``` Restore a backup of 2.7GB zmbackup -r -ro full-20200301010607 user@example.com user-restore@example.com Error : Error message below:/usr/lib/python2.7/site-packages/urllib3/connectionpool.py:769 Restore a backup of 1.9GB zmbackup -r -ro full-20200401010607 user@example.com user-restore@example.com it works ``` <!-- ACTUAL RESULTS: What happened when you did the steps before. --> ##### ACTUAL RESULTS ``` I tried with other backups 3GB and 800MB and the same results : - Larger than 2GB : Error - Lesser than 2GB : Works I used strace, and I found that there is an overflowerror : read(3, "\nhttp: error: overflowerror: str" Reading about httpie, it seems it does not support uploading files larger than 2GB. The latest version of htpie 2.2.0 does not have support for lager files, this feature is meant to be available on httpie 2.3 which is in dev for now. Since zmbackup is a bunch of bash scripts, could we use another tool other than httpie to upload larger files? ```
kerem 2026-02-27 08:14:26 +03:00
Author
Owner

@bezunartea commented on GitHub (Nov 28, 2020):

I also stumbled upon this issue, I have a few accounts whose backup files are well over 2GB, and cannot be restored... which actually defeats the main purpose for a backup. A backup file is totally useless when it cannot be restored.

I'm surprised that the actual recovery command is run as an http request to the web server. I guess there is no command line in zimbra for this purpose right?

<!-- gh-comment-id:735034259 --> @bezunartea commented on GitHub (Nov 28, 2020): I also stumbled upon this issue, I have a few accounts whose backup files are well over 2GB, and cannot be restored... which actually defeats the main purpose for a backup. A backup file is totally useless when it cannot be restored. I'm surprised that the actual recovery command is run as an http request to the web server. I guess there is no command line in zimbra for this purpose right?
Author
Owner

@lucascbeyeler commented on GitHub (Dec 6, 2020):

Hi, actually there is - on the enterprise. Which defeats the purpose of the zmbackup if you can pay for the enterprise...

<!-- gh-comment-id:739490644 --> @lucascbeyeler commented on GitHub (Dec 6, 2020): Hi, actually there is - on the enterprise. Which defeats the purpose of the zmbackup if you can pay for the enterprise...
Author
Owner

@lucascbeyeler commented on GitHub (Dec 8, 2020):

Fixed - stopped using httpie and instead I'm using back cURL. Closing ticket - a new release with cURL enabled will be available at the end of the day.

<!-- gh-comment-id:740643221 --> @lucascbeyeler commented on GitHub (Dec 8, 2020): Fixed - stopped using httpie and instead I'm using back cURL. Closing ticket - a new release with cURL enabled will be available at the end of the day.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/zmbackup#119
No description provided.