Skip to content
This repository has been archived by the owner on Jun 19, 2024. It is now read-only.

Better idempotency and failure protection #2

Open
scotte opened this issue Jul 11, 2018 · 0 comments
Open

Better idempotency and failure protection #2

scotte opened this issue Jul 11, 2018 · 0 comments

Comments

@scotte
Copy link
Owner

scotte commented Jul 11, 2018

Currently, there's little (no) logic to handle things such as a snapshot already existing (which should just be used, instead of failing), cleaning up the bind mount if the borg create operation fails, handling when a borg backup already exists with the same name, etc. Ideally, running borgsnap is idempotent and consistent.

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

No branches or pull requests

1 participant