Capacity Tier encryption and object storage size considerations

[TRE3]

Hello!

We have a customer who uses a Scale-out repository with Capacity Tier offload - not encrypted. He now wants to encrypt the data and has the following question:

Will the newly encrypted object storage data be recognized by the existing not encrypted data in terms of deduplication or will the newly uploaded and encrypted data blocks be recognized as "new" data blocks that cannot be deduplicated with the existing non-encrypted data blocks (which will lead to a doubling of object storage data)?

Thanks!

[veremin]

If you enable encryption, a job will create a new full backup during its next cycle. New full restore point will not be deduplicated with the existing unencrypted data residing in capacity tier. Thanks!

[Petzi]

Hello,

an additional question:
If i have enabled encryption (only in Capacity Tier) and change the encryption password, is there also a full backup nessesary?
And will all blocks have to be uploades again? Or does deduplication works over different passwords?

Veeam says, ist's best practice to change the password ... but how can deduplication work if blocks change?

Thanks

Rainer

[veremin]

If i have enabled encryption (only in Capacity Tier) and change the encryption password, is there also a full backup nessesary?

No, it is not. Thanks!

[Petzi]

Thanks.

And what's about deduplication?

Rainer

[veremin]

If by deduplication you refer to forward incremental nature of Capacity Tier (already transferred blocks are not transferred again), then the answer is yes, it will be preserved. Thanks!