SOBR Retention Policy and Archive Setup

[no_leaf]

Hi,

I'm new to forum and upto now I've found very usefull answers for the situations I had. But this time I need your opinions how to configure a backup plan as I described below.
It is a little bit related that I couldn't get the logic of options.

I created monthly full backup, pointed to Azure SOBR and I want to keep monthly backup only 1 month locally but keep off-site backups monthly 12 Months and yearly 3 Years.

Here is the config screenshots

SOBR Capacity Tier:
0 Days selected to an immediate upload to Azure Blob Storage



Full Backup Job Config:
At this point I assume this setting will keep monthly full backup only for 1 month locally.
But not sure about the archival purposes selection handle my request. Does that mean after 1 month; it will upload to off-site but again keep it both local and off-site as defined?



Does it also keep local and off-site backups for same period of time?
If not what will be the correct to keep only on off-site monthly 12 months and yearly 3 years?

Thanks.

[HannesK]

Hello,
and welcome to the forums.

Your "Full Backup Job Config:" looks strange / inefficient to me. The software is designed that one backup job does full backups, incremental backups and GFS restore points. I see "1" restore point and I assume some schedule that creates something unpredictable without seeing the whole configuration.

I want to keep monthly backup only 1 month locally but keep off-site backups monthly 12 Months and yearly 3 Years.

that would mean one backup job with the following settings:
- forward incremental with synthetic (alternatively active) full backups. That's the default setting (just in case you changed it)
- I recommend weekly synthetic full backups on REFS / XFS file system
- retention: 30 days (so I don't need to worry about schedule)
- Keep certain full backups... 12 monthly / 3 yearly as shown in the screenshot

For the scale out repository capacity tier
- move is correct (as shown in screenshot). Move backups older 30 days (not 0)

Best regards,
Hannes

[no_leaf]

Hi Hannes,
Thank you very much for the reply.

I have also different backup jobs running locally with forward incremental type as usual as others but this one is only a specific requirement for a vm.

This is the Backup Setting Job, instead creating synthetic full backup I selected Active full backup for all months. Config may countable as not changed.

- retention: 30 days (so I don't need to worry about schedule)

So, since it will run monthly;
- 30 days will stand for actually 30 months. As far as I know "days" counted for when job runs, correct?
- Or otherwise is that same to select 30 restore points?
- Why we select days instead of restore points?

For the scale out repository capacity tier
- move is correct (as shown in screenshot). Move backups older 30 days (not 0)

Is this because we select 30 days as retention?

With my current config, what will be the outcome of it? Maybe If I understand current config's result than it will be easier for me to get it.

Thank you,
no_leaf

[HannesK]

Hello,
okay, if you run the job only monthly, then the approach would work with the configuration shown above. Whether you move after 0 or 30 days makes no difference, because there will always be one full on-prem.

My other suggestion came from the background, that new Veeam customers sometimes try to do things they did in a different software before.

Best regards,
Hannes

[no_leaf]

Hi Hanna,

Thank you, and you are also correct old habits sometimes can be challenging.