borgsnap
borgsnap copied to clipboard
Better idempotency and failure protection
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.