Backup retention

[raffapol]

Hello Forum!
I'm facing a customer request regarding retention policy on his MS Organization backed up on our systems.
The point is that he used ti have monthly full and daily incremental.
With VOB365 I'm only able to offer incrementals. Someone wrote me that the criteria are different, but I can't understand how. Just for example - after 3 years, with a chain so long, what if the original full get corrupted?
Thank you for explaining me (and me, for explaining to customer).
Cheers
Raff

[Polina]

Hi Raff,

There's no physical chain of backup files in VB365. We get the initial state of each item on the first full and each subsequent increment saves a new state of this item (while previous states are preserved). You cannot delete or corrupt the initial full backup file, because it doesn't exist as a file.
I assume you're already familiar with the VB365 repositories structure, but just in case here are the links to the HelpCenter where it's explained:
Jet-based repositories: https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=70
Object storage: https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=70

Thanks

[raffapol]

Thank you for the links, they clarified me the behaviour of this backup.

So, if I undrestood, there's no a chain, and a full "single file" because the first full actually is a copy of all the objects inside the organozation backed up, so it's not a file but a big numner of files. That aren't touched since all the subsequent jobs are incremental.

Let me ask you smthg about a doubt I still have, comparing with "traditional" full: what is a mail backed up on the first full, during the months get corrupted for any reason (HW failure?), in case of a traditional full I still have other full to rely on - in this case I only have a copy. Am I wrong?

Thank you Polina
Cheers
Raff