borgsnap icon indicating copy to clipboard operation
borgsnap copied to clipboard

Better idempotency and failure protection

Open scotte opened this issue 6 years ago • 0 comments

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.

scotte avatar Jul 11 '18 16:07 scotte