space occupied on S3

[mporliod]

How does Veeam manage the space occupied on S3? Suppose I configure a Scale-Out Repository with a local repository and an S3 repository. If I apply a 7-day retention policy with a weekly full backup, will the space occupied on S3 be the same as on the local repository when using the "Copy" mode? Or does the second full backup on S3 leverage block cloning?

Additionally, if I perform the backup directly to S3 without using the Scale-Out Repository, does Veeam create only the first full backup, followed exclusively by incremental backups?

Thank you.

[Gostev]

While the term "block cloning" term only makes sense when talking about file systems and files (between which those block are cloned), and does not make any sense whatsoever for object storage, which does not have a file system and so there are no files in the first place -

AND DESPITE THE FOLLOWING BEING COMPLETELY TECHNICALLY WRONG

for the sake of simplicity you can think that when working with object storage, Veeam does everything at all with block cloning.

It's a terribly wrong way to say simply because none of the above things you mentioned (like first full backup, second full backup, incremental backup) applies to object storage, as there are no backup files to begin with... it is an entirely different storage paradigm. But since ultimately you're asking about the resulting occupied space, you can just think it's all block cloning all the way and for everything