mirror of
https://github.com/lucascbeyeler/zmbackup.git
synced 2026-04-24 22:55:56 +03:00
[GH-ISSUE #193] Readme should list scope #154
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#154
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 @FlorianHeigl on GitHub (Feb 18, 2026).
Original GitHub issue: https://github.com/lucascbeyeler/zmbackup/issues/193
Hi,
I would think it helpful if the readme had a table of things that are restored and those which aren't.
first reason, settings and stuff...
the fact that the config is not stored with the backup differs from the old NE backup mechanism and one ought to know (and can then react and maybe use etckepper on etc conf dirs)
secondary reason...
i.e. a backup of all mailboxes is documented (-m -all), but a restore isn't.
since it also fried my ldap or at the very least had a progressive influence on the passwords of some sort, I feel life would be easier if there was some clearer overview as to what is being touched and what isn't.
@FlorianHeigl commented on GitHub (Feb 18, 2026):
ok i'll add one. in light of #160 there should be an instruction how to just restore everything from a full backup without destroying ldap?! :-)
from what I see, -r <full_backup_id> is not it.