Re: setting up an autochange in the cloud

Am 21.10.24 um 17:15 schrieb Bill Arlofski via Bacula-users:

> Not sure I would call FD encryption plus SD encryption "better", only 
> because you have the added task of managing the keys/certs on the 
> client(s) in addition to the SD re-encrypting the already FD-encrypted 
> data and you needing to make sure the encryption key files for each SD- 
> encrypted cloud volume are safely maintained. :)
> 
> So, more CPU use on client(s). and on SD, and more admin work, but yes, 
> data would be encrypted twice in such a setup.

So I assume you say, it's enough to enable it in SD, right?
And let the FD encryption away to keep it simple(r).

?
  > In addition to setting "Volume Encryption = yes" in each of your your
> SD's c
> loud devices, you also need the following in your SD's top-level 
> configuration:
> ----8<----
> EncryptionCommand = "/path/to/key-manager.py getkey"
> ----8<----
> 
> The actual path will depend on the Bacula community maintainer for your 
> distro. :)

Yes, that was what I was missing (and the installed package, sure). I 
added/check both things according to the mentioned video.

Now it works.

thanks to both of you!