nssbackup-team team mailing list archive

[Jean-Peer Lorenz <616497@xxxxxxxxxxxxxxxxxx>]

Thanks for using nssbackup and for reporting this issue.

Well, good catch. I've never looked at the exact wording of the purge option.
I'd say it should get reformulated into 'Remove old snapshots' instead of 'Remove old and incomplete snapshots' as it reads now.

Let me explain why I think so: Usually, one should never get corrupted
snapshots. If everything works fine only valid snapshots should exist
and were removed after the specified period of time (if they are
standalone snapshots, i.e. do not build the base for subsequent
incremental snapshots). If you got corrupted snapshots something went
wrong: maybe a file in the snapshot was renamed by accident when viewing
the content of the snapshot directory or the backup was interrupted. If
this happens one *could* maybe want to recover the snapshot manually. If
this is not desired the corrupt snapshots (i.e. the directories) can be
deleted easily and without problems. Because of this possibilty I'm
against automatic removal of corrupt snapshots - it could still contain
valueable data.

To improve/simplify the removal of such corrupt snapshots we could add a
function to the snapshot management section in the restoration GUI. User
could then clean their backup destination in an explicit way from there.

What do you think?

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

** Changed in: nssbackup
       Status: Opinion => Confirmed

-- 
nssbackup is not cleaning up old, corrupt backups
https://bugs.launchpad.net/bugs/616497
You received this bug notification because you are a member of NSsbackup
team, which is subscribed to NSsbackup.