ok my favorite feature of Bacula 15 is that you can now define Allowed Backup Directories on the File Daemons (clients) and have a rule on the Director that just says to backup everything by default, so then you can just tune it per-client.
If I want to change what gets backed up on my laptop next scheduled backup run, I don't have to touch the server.
Blurry Moon
in reply to feld • • •frontends yet
feld
in reply to Blurry Moon • • •feld
in reply to feld • • •@sun I have the beginning of a custom Elixir client that could be used with LiveView but I got stuck at a spot with TLS upgrade with their custom communication protocol and didn't go back to it yet
There's basically no 3rd party tools that talk directly to the Director server because their protocol is not documented, it's whatever the existing client does. So I was gonna reverse engineer that with the help of Claude
fuzzyfuzzyfungus
in reply to feld • • •Does doing it this way provide the server with the locally-defined policy that a given backup is intended to reflect(the way only using server-defined policy does sort of incidentally) or is knowing that up to you?
I can definitely see the utility for situations with deliberately lightly managed endpoints where backup is more of an offer; but in the shoes of the person being asked if The Policy is being applied to all 1000 clients I'd want to be real sure about that detail.
feld
in reply to fuzzyfuzzyfungus • • •