s3 object storage repository - switch storage class from standard to ia

[VNR-LF]

hi all,

we have started using vbo more than a year ago and set our repositories to offload backup data to s3 object storage repositories. initially, we decided to not use the infrequent access storage class but the standard storage class. right now, we would like to change this, but also keep all backup data currently present in our repositories accessible.
is it possible to change an already existing s3 object storage repository to use the ia storage class? alternatively, will it cause any problems for the backup application if i create a lifecycle rule on the s3 bucket that transitions all objects to standard-ia?

thanks in advance and kind regards,
lars

[lokeshselvam]

Hi,

By default, the storage class in s3 is STANDARD. However, you could opt for a different storage class .S3 storage classes allow lifecycle management (lifecycle rule)for automatic migration of objects for cost savings . These policies have nothing to do with the backup software.

[Mildur]

Lifecycle policies on the bucket are not supported with veeam.
Enabling Lifecycle Management could lead to unexpected backup or restore failures.

[Mike Resseler]

In the meantime, this is a supported scenario if you want to move data from one object storage repository to another. So instead of changing the class, create a new bucket / folder / ... with different class and perform the following migration:

1) Create new OSR Repository
2) Make sure the old OSR Repository is disconnected (during the copy/paste, no new data should be written there)
2) Copy\Paste folder with backup data to new OSR repository. (Please use the correct tools to do this, depending on the storage vendor )
3) Attach copied data as new OSR (without persistent cache).
4) Change target of backup job to new repository.
5) Start incremental backup.

[Mike Resseler]

Hi all, I know this is an old topic, but it is noticed that in some cases corruption appears after copying the data with native tools. We noticed that not always everything is copied which then can result in a corrupt repository.