nssbackup-team team mailing list archive

[BlueLight <622496@xxxxxxxxxxxxxxxxxx>]

Since sbackup and later nssbackup and much later nsbackup has been
developed with a normal user in mind (as far as I understood) and since
it deal with backups which I consider a VERY important thing to have an
unnoticed backup failure needs to be avoided under any circumstances.
For technicians like me to be called in if a user looses a config file
is bothersome because it might be my mother-in-law or many other people
whom I want or don't want to see too often.

If a backup is started or scheduled and it can't find the destination
drive it should come up with a clear big red flashing warning and give
the user a precise information what to do. And in case that doesn't
happen not to loose the config file. A backup that is saved by default
on the same harddrive is not a backup if that harddrive crashes.

I don't feel compfortable to configure Ubuntu machines with nssbackup
when I know that the config file can be lost. External drives as Igor
points outs rightly is the prefered backup medium for many Desktop users
and all Notebook and laptop users. I believe that that is reason enough
to take this issue further in the programming and find a solution.

-- 
problem occurs if nssbackup is run with the destination drive not present. It looses the config info.
https://bugs.launchpad.net/bugs/622496
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.