>Hello All,
>
>
>I’ve set up a bacula server to do backups of some 10 systems. It’s a small-scale test setup to serve as a proof of concept and testing ground for >a to-be-deployed larger setup (~300-400 systems).
>I have those clients, in this case a server named “almond”, with it’s own Device ( a ZFS filesystem), it’s own Storage and Pool definitions >etc. (Please note: I’m testing with making a configuration wherein each client has it’s own pool/storage/device in it’s own zfs filesystem. In the >current config, almond is the only client for which this is configured like this. This shouldn’t
change anything though) The config is below. >This setup works very well, I can do parallel backups etc. and have great control over retention etc. The problem is that all clients that use that >Director can do restore actions to themselves of data from any other client.
I'm not sure how yours is set up, but on mine I had to go out of my way to make it possible for clients to do any restores.
On the client, I had to
create a bconsole.conf, such as:
Director {
Name = bacula-dir
DIRport = 9101
address = bacula-server
Password = "someBigUglyPasswordWitchMatchesTheOneOnTheBaculaServer"
}
