Configuration to retention

[vitor.pires]

Hi everbody
I'm using veeam b&r v10. My backup job is configured like this:
Retention policy: 10 restore points
keep monthly full backups for 60 months
Backup repository is Scaleout
Scale out to aws Move backup files older than 10 days

Does this configuration Is correct to archive my vms?
I need at least one backup to be archive every month, if another path is better please help me
Thank so much

[HannesK]

Hello,
and welcome forums.

Does this configuration Is correct to archive my vms?

It will archive. So I would answer with yes

I would add the copy checkbox to make sure, that you have a copy of your backups in case you loose the local repository. (3-2-1 rule https://www.veeam.com/blog/how-to-follo ... ation.html)

Best regards,
Hannes

[oleg.feoktistov]

Hi Vitor and Welcome to the Community Forums!

If we are talking 10 daily restore points retention, looks correct. I'd also increase operational restore window to 12-14 days just in case
some backups fail and we are bound to wait for their successful completion to fulfil retention policy as described here.

Thanks,
Oleg

[vitor.pires]

Hi Oleg thank so much for help me.
My job run once daily 22h, so I have 10 restore points to 10 days, its correct?
Will be work my retention?

[vitor.pires]

Hi Hannesk thank you so much
I agree with your idea about copy, but storage space maybe be a problem or not? If check copy backup as soon as created all copies will like job, for example, saturday will copy full to capacity tier, in the week copy incremental,next saturday will copy full again. Its correct? If all copies after full are incremental forever there is no problem. About retention, will be 10 restore points too like job?

[oleg.feoktistov]

Vitor,

My job run once daily 22h, so I have 10 restore points to 10 days, its correct?

Yes, that's correct.

If check copy backup as soon as created all copies will like job, for example, saturday will copy full to capacity tier, in the week copy incremental,next saturday will copy full again. Its correct?

Capacity tier works in forever forward incremental fashion. Only changed blocks are being offloaded.
If you combine copy and move modes, after operational restore window is exceeded, in inactive backup chain data blocks will just be removed from backup files on performance tier as they were already offloaded to capacity earlier in scope of copy policy. Only metadata will be kept.

Best regards,
Oleg