Hi Morty, Excerpts from Morty Abzug's message of 2010-05-04 19:33:12 +0200: > (1) no way to do a simple client check (AKA amcheck -c.) > (2) no way to do a simple tape check (AKA amcheck -lt) What exactly do you mean with "client check" and "tape check"?
> (4) no way to logically group hosts into a "run", with common options, the > way amanda can. Somewhat solvable with scripting. You can use template files and replace variables therein with sed, like this: @"|sed 's/%name/client-1/g' /etc/bacula/client.tmpl" While it looks ugly (especially with many variables), it’s a good method to simplify your configuration considerably and keep boiler-plate to a minimum. > (6) no proper client/server model. bacula "clients" need inbound ports Why would one want a "proper" client/server model? Not having the need to contact the director all the time is actually good, IMO (you would have to do that when not having inbound connections). Also, for the storage daemon it is quite clear that it needs inbound connections (it has to directly communicate with the fd, so at least one of them needs inbound connections). The director itself does not need inbound connections (AFAIK). I guess you want to get rid of inbound connections because you are behind a NAT. The better solution would be to get rid of the NAT or at least use IPv6 to have a proper internet connection. NAT makes all kinds of things ugly and requires lots of strange workarounds. > (7) no support for native backups. What are "native backups"? > (8) no built-in support for fully-automated storage of recovery data. > bacula recovery disks require a lot of manual work. Not sure if I understand your point, but for a bacula recovery disk you just need any linux live system (grml.org comes to mind) and edit bacula-fd.conf exactly once. That’s not a lot of manual work, IMO. > (9) no support for TOFU authentication. Clients must be hand-configured. What is TOFU authentication? What prevents you from using some automated configuration system like puppet to roll out your config? > (12) bconsole should support an option for execute-one-command (i.e. -e) You can pipe commands into bconsole. > (13) bconsole should support an option for batch mode (i.e. -b) See above. > (14) no support for "disable job=$job until $time" You can use at(1) and bconsole, see above. Best regards, Michael ------------------------------------------------------------------------------ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
