[Nssbackup-team] [Bug 622496] Re: problem occurs if nssbackup is run with the destination drive not present. It looses the config info.

[barinov2000]

Well,

The way it works NOW: you get error message and then you have to click
OK, plug in the missing media, reconfigure backup, run backup

only tech savvy people will put up with that.

The way it SHOULD run is: you get message informing that the media is
missing and asking you to plug it in and to click OK button and the
backup continues, or click Cancel which takes you to selection of
another media, and maybe another button - remind in x minutes.

Many people have external hard drives which are not plugged in all the
time and getting an error (or not getting an error and not doing a
backup)

People want GUI backup because they want the ease of use, and the
current workaround IMHO is not much user-friendlier than using CLI.

-- 
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.

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp

Re: [Nssbackup-team] [Bug 622496] Re: problem occurs if nssbackup is run with the destination drive not present. It looses the config info.

[Anton]

Hi,


May I add something, that I stumbled on the other day. I do some of my 
backups on an external disk at home. But I might at some point want to 
review (and tweak) my settings while away from that disk (say, in a 
spare 10 minutes in the train or so). Currently this is not possible, 
since SBackup will complain about the missing backup destination, and 
re-insert the default. Worse, if I didn't read the message carefully 
enough (or not at all), and Save the configuration, I've messed up my 
settings.

I think the message should give the user the option to keep the current 
(correct) setting, or to change it (choose a new location), or set it to 
default.

P.S., the same goes for my other backup setting, where the destination 
is a server at the university that I can only reach from inside 
(firewall protection).

This opens the problem that Jean-Peer raised, to make sure the backup 
location is always a valid one when it is saved. Would it be good enough 
to display a warning for a saving a destination location that cannot be 
(currently) validated?

Alternatively, this may be a separate configuration option, something 
like allow un-tested destination location to be saved?.


Groetjes,

Anton.

-- 
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.

___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help   : https://help.launchpad.net/ListHelp