30 Dec
2013
30 Dec
'13
8:05 p.m.
On Dec 30, 2013, at 7:27pm, Ross Younger <ross(a)impropriety.org.uk> wrote:
On 31/12/13 04:49, Andy Smith wrote:
This sounds like the best option, although perhaps a slightly simpler-to-build approach
would be to just automatically delete the oldest backup (despite the schedule choices) to
make space for the larger new ones, a la OS X's Time Machine, though I'd like to
be notified if this occurs so I can take action to fix it.
Which of these makes the most sense?
Should both options exist for people to choose between?
As a user I'd personally go for suspend-with-alert, but I do wonder whether
automatic-extend would be preferable for some? I guess it's down to what the users
want, bearing in mind that 38 customers isn't worth spending too much time on ;-)
If I implemented a way (from the Panel) to nuke
the most recent set
of backups then would that make the "suspend" option the best one as
the customer can still fix it themselves?
I like the sound of this. In an ideal world (pie in the sky etc etc) the panel would show
me a simple listing of the backup sets - timestamp and size - and allow me to blow any of
them away; this covers the case that some large file was accidentally backed up a few runs
ago.