mirror of
https://github.com/lucascbeyeler/zmbackup.git
synced 2026-04-24 22:55:56 +03:00
[GH-ISSUE #127] A warning, this backup tool may not be reliable #97
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#97
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 @ghost on GitHub (Feb 7, 2019).
Original GitHub issue: https://github.com/lucascbeyeler/zmbackup/issues/127
Originally assigned to: @lucascbeyeler on GitHub.
Hello All,
It seems this backup tool relies on exporting mailboxes using the Zimbra REST API
https://github.com/Zmbackup/zmbackup/blob/1.2-version/project/lib/bash/ParallelAction.sh#L48
This has been known to be unreliable, and may cause corrupted backups.
https://bugzilla.zimbra.com/show_bug.cgi?id=101760
https://bugzilla.zimbra.com/show_bug.cgi?id=86347
The tgz option shoud be fixed before one can use backup tools like the one in this repo. This has been confirmed by Zimbra staff in the bugzilla reports.
Barry
@enribar commented on GitHub (Feb 15, 2019):
Hello Barry,
do you know if there are any free backup alternatives other than using Zimbra REST APIs?
@ghost commented on GitHub (Feb 15, 2019):
Unfortunately I do not think there is one.
Someone should get dirty hands and fix the parts in Zimbra that break the export, I can imagine pathing the java so that it throws an account to a folder instead of a tgz. From there we can have a different process make the tgz.
Then we could debug the import process, I am not 100% sure how broken that is.
So the export, is I think fixable. It just needs someone to put the time in.
@vadonka commented on GitHub (Jun 27, 2019):
The project is abandoned? It seems to. No words from the dev?
@ghost commented on GitHub (Jun 27, 2019):
looks like so
@vadonka commented on GitHub (Jun 27, 2019):
I guess i need to rewrite the backup/restore part to use the zmmailbox api and not the wget/curl method.
@ananiasfilho commented on GitHub (Jul 28, 2019):
Hello guys! The project is stoped but not die! Lucas move from Brazil to Ireland and have a lot of things to do before back to zmbackup development. The version 2 will came this year. Im working hard on new zimbra 2 all re-write and using python3.
I will dedicate this week to check issues and feedback all of you. Feel free to fork project and send Pull requests.
@lucascbeyeler commented on GitHub (Dec 8, 2020):
Hi,
Good to know that Zimbra is breaking the backups for no reason. The only solution I can see for this would be reverse engineer Zimbra to generate the tgz files by ourselves. I'm moving this idea to Waddles as I will continue developing Zmbackup as a Python solution.