Scale-Out Capacity Tier Retention

[warnox]

Hi,

I'm just wondering how retention on the capacity tier for scale-out repositories works.

1. If my backup jobs are configured to keep 7 restore points and the scale-out repo is configured to copy the backups to object storage immediately. Will 7 restore points be available in scale-out repo object storage and the same 7 locally?
2. Same as above, but I set immutability for object storage to 30 days; will object storage end up with 30 days of backups and only 7 will be kept locally?

Thanks for any input.

[HannesK]

Hello,
the retention works exactly the same like on local repositories.

1. yes, that's why it is called "copy"
2. it will end up with errors. It's not possible to enforce 30 days and 7 days retention at the same time. The immutable time must be lower than the backup job retention time.

Best regards,
Hannes

[warnox]

Thanks.

Maybe it should warn you if you try to do that as it definitely lets you

[hoang92bn]

so, what happen with data on Object Storage when Retention when backup job is begun? @HannesK

[HannesK]

I'm not sure I understand the question.

Imagine performance tier + capacity tier as one repository. Ignore the fact, that there are two technologies involved.

The retention is applied as configured in the backup (copy) job.

And it is a good idea to not break with with too high immutability settings