archiving GFS

[balma01]

After you enable the GFS retention, the backup chain switches from the forever-forward incremental policy to forward incremental policy.
So the GFS fulls are part of a chain with some incrementals.
What happens if an archive job moves a GFS full to the archive tier? The backup chain seems to be broken, because the full is moved away...
Am I wrong?

[HannesK]

Hello,
short answer to your last question: yes

Longer answer: the software only moves inactive chains. https://helpcenter.veeam.com/docs/backu ... ml?ver=110

And it only moves to capacity tier (from performance tier). See FAQ: post338749.html#p338749

Best regards,
Hannes

[balma01]

Hi and thanks,
I'm speaking about archiving from capacity tier to archive tier not from performance to capacity

[veremin]

Scale-out Backup Repository consists of several layers: Performance Tier, Capacity Tier and Archive Tier. The GFS restore points will be moved to Capacity Tier first and only then to Archive Tier.

As Hannes said, the backup server will wait till GFS restore point become inactive and fall out of the specified operational restore window and only then move them to Capacity Tier. So there will be no active GFS restore points: neither on Capacity nor on Archive Tier.

Thanks!

[balma01]

Hi and thanks
Suppose to have a forward incremental backup
As far as I know The backup server will wait a backup chain become inactive and fall out of the specified operational restore window and only then move the entire to Capacity Tier
Then from the capacity to the Archive tier, the entire chain is not moved but only the full.
So, at the end, in the capacity tier we have a chain of incrementals without a full that has been moved to the archive.

[Mildur]

Then from the capacity to the Archive tier, the entire chain is not moved but only the full.
So, at the end, in the capacity tier we have a chain of incrementals without a full that has been moved to the archive.

Veeam will never remove something what is needed todo a restore. I think they have their logic programmed into the software to workaround that scenario.

[Gostev]

You should start from not thinking in terms of backup files and backup file chains here. Backup files is a thing with classic storage only, so you should literally forget everything you learned in the past years about the way Veeam stores backups in files. Trust me, it will really help the understanding to forget everything you knew! Because object storage does not have a file system in the first place, so neither there are backup files. Likewise, offloading a full backup does not means moving a file from one repository to another, like it is with classic storage. Instead, all operations are done at the object level, and individual objects are never removed as long as they are used in at least one restore point.

[balma01]

Thanks Gostev
Maybe 'veeam and object sorage under the hood' can be one of your next newsletters...