Re: setting up an autochange in the cloud

Am 11.10.24 um 20:41 schrieb Marcin Haba:
> Hello Stefan,
> 
> On Fri, 11 Oct 2024 at 20:26, Stefan G. Weichinger <[email protected]> wrote:
>> did that, it seems to do something now ;-)
> 
> Super :-)
> 
>> Do I understand correctly that it writes in to "/tmp/$somevol" at first
>> and then uploads data to the cloud?
> 
> Yes, in short. It writes volumes locally (local cache) and uploads to
> the cloud as well. In the Cloud resource 'Upload' directive you can
> define when the volume parts will be sent to the cloud. The
> TruncateCache directive is for defining what to do with local volume
> parts.
> 
>> I might play and learn a bit more and come back with more sophisticated
>> questions, maybe.
> 
> Don't worry. This user list is exactly for that - for asking questions
> and helping users :-)

great, thanks a lot

I now have a new question ;-)

I set up data encryption in the file deamon reading from my desktop 
machine. Seems to work, backup and restore (using a file-based changer 
locally on a server).

What if I use this with cloud storage?

There is an option "Volume encryption" in the cloud storage resource, I 
assume this would be redundant, right?

As far as I understand if the fd delivers encrypted data, it goes 
encrypted to the cloud storage, right?

I want to get that right before putting my data out there unencrypted ...

thanks!