mirror of
https://github.com/lucascbeyeler/zmbackup.git
synced 2026-04-25 07:05:55 +03:00
[GH-ISSUE #151] Backups lager than 2GB cannot be restored. #119
Labels
No labels
Bug Report
Enhancement
Enhancement
Feature Idea
Feature Idea
Not Implemented
Question
Question
Task
Wontfix
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/zmbackup#119
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
ENVIRONMENT VERSION
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
ACTUAL RESULTS
@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?
@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...
@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.