Why is S3 immutable retention max 90 days?

[darren.flatman]

I need to keep 6 years of immutable backups in AWS S3 cloud storage
I mapped in the AWS bucket
When I choose the immutable option, the max number of days is 90
Object lock for AWS can be indefinite, or you can set a life cycle but this option needs to be disabled when mapping in to Veeam
Is there a reason the max number of days when adding the repository to Veeam is 90? and if possible can this be changed?

[Mildur]

Hi Darren

I assume it‘s to protect yourself from higher costs.
If you need more than 90 days, you can use powershell to extend this to a higher value. If I remember correctly, you can set a max value of 999 days for the capacity tier over powershell.

But I recommend to consider using Veeams Archive Tier if you need 6 years immutability. The costs are much lower for Amazon S3 Glacier as for the Amazon S3 Buckets. Long time immutability should be done in the archive tier and not in the capacity tier. You can set immutability for the entire retention period of the gfs restore points in the archive tier.

Code: Select all

Set-VBRAmazonS3Repository -Repository <VBRAmazonS3Repository> -ImmutabilityPeriod <int32>

https://helpcenter.veeam.com/docs/backu ... ml?ver=110

[darren.flatman]

Thanks very much this looks like it will work

[BHi]

Hi,

is there any option for S3 Object Storage?

Get-VBRObjectStorageRepository is usable, but there is no Set-VBRObjectStorageRepository option available.

[Mildur]

Yes. It's another command for S3 compatible object storage.

Code: Select all

Set-VBRAmazonS3CompatibleRepository

https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Best,
Fabian

[BHi]

Thanks, it works.