>>> Bacula does have root read (and write) privileges on every backed-up system, >>> but you can encrypt the backups before sending them to the central server. >>> Bacula can also sign the backups, so the client can verify that a restore >>> doesn't contain modified data. You still have to keep the >>> encryption/signing >>> keys secure of course. >> >> Thanks for your help. I don't think I have the b*lls to give root >> read/write on every system to the backup server. :) >> >> - Grant > > You are free to operate the FD (Client) with any permission you like, > but you have to take care that the FD is able to read anything you > like to backup and i case of restore it should be able to write and > maybe to "chown" the files in question.
I may have misunderstood before. The FD runs on the client machines, correct? Read and writing to localhost is no problem. What worries me is one machine having root read(/write) permission on another machine. Can bacula operate without that? - Grant ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users