nssbackup-team team mailing list archive

[Jean-Peer Lorenz <913827@xxxxxxxxxxxxxxxxxx>]

Thank you for using sbackup and for taking the time reporting this bug.

The order of backup creation and removal of existing snapshots was choosen by intent:
1. make a new backup
2. in case of success remove old snapshots

Reason for this is, that you don't want to end with *no* backup at all
in case of errors. Image following situation: all snapshots were removed
(since they are older than the specified threshold). The subsequent
backup fails for whatever reason. You'd have lost all of your backups
now and this is not acceptable.

I set this issue to Opinion and please feel free to add comments or
elaborate on your usecase or possible solutions from user's perspective.
There is room for improvements here but simply change the order of
backup creation and removal is not the right solution, I think.

Thank you so much for your help.

** Changed in: sbackup
       Status: New => Opinion

** Changed in: sbackup
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/913827

Title:
  should delete old backups, then create new / not enough space on media

To manage notifications about this bug go to:
https://bugs.launchpad.net/sbackup/+bug/913827/+subscriptions