Hello there.
I'm wondering if there is any less-intrusive option for backing up
"interminnently connected" hosts (like my wife's laptop :-)).
At first I had a static schedule which would backup the client every day
at 9am or so.
That of course would make backups skipped if the laptop was not on at
that precise time so I had to monitor that externally and sometimes
spawn backup jobs manually. That was annoying.
Then I found the "Run On Incoming Connect Interval" option which made my
life much easier. Now if the "normal" backup job is skipped, the backup
gets spawned as soon as my wife boots up the laptop. That makes it
relatively well covered in terms of backup.
But it also makes the laptop unuseable (especialy in terms of
videoconference solutions or other low-latency uses) for the first half
hour or so after each bootup.
So the question is - is there any reasonable way to make the backups
more client-controlled? So the backup job is not spawn immediately after
the connection from fd to dir, but can be delayed by user or spawned
directly by user when desired?
I probably could set up the bareos webui but could I limit my wife's
permissions to just that single client? It would still not be a very
elegant solution (the necessity to log in to "external" service is not
very user-friendly) but it would be something.
Any other paths to explore?
I'm at 20.0.1 at the moment.
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/7a7f7777-6586-a08a-0a7b-051c6db72ecb%40gmail.com.