Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mention limitation of borgmatic extract #522

Open
felixoi opened this issue Jan 26, 2023 · 0 comments
Open

Mention limitation of borgmatic extract #522

felixoi opened this issue Jan 26, 2023 · 0 comments

Comments

@felixoi
Copy link

felixoi commented Jan 26, 2023

I ran into an issue while restoring to a backup using borgmatic as described in the docs (documented in a community post). Basically this issue occured because of a limitation of borg backup:

"borg extract only supports restoring into an empty destination. After that, the destination will exactly have the contents of the extracted archive. If you extract into a non-empty destination, borg will (for example) not remove files which are in the destination, but not in the archive." (source)

As of the mailcow docs restoring the maildir is done using

docker-compose exec borgmatic-mailcow borgmatic extract --path mnt/source --archive latest

. This makes it important to mention the limitation, otherwise duplicates or similar may occur.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant