Offload backup failure

[Fenikas]

Hello everyone,

Have an issue lately with my offload AWS backups. I keep getting:
REST API error: 'S3 error: The operation is not valid for the object's storage class
Code: InvalidObjectState', error code: 403
Other: StorageClass: 'DEEP_ARCHIVE'

I put in a ticket with veeam and they informed that the original setup was not correct. That the setup doesn't support Deep Archive, but after retracing my steps, there is no Deep_archive in my Veeam/AWS setup. Once the data is in my normal S3 bucket, after 2 days, it will be deep archived.

None of the AWS storage repositories are setup as glacier or deep archive. Just normal S3 buckets. I don't know why this error is occurring.

[nielsengelen]

Hi Kenny, to verify - you are using Veeam Backup for AWS?

Can you tell me what schedule you have configured?

[Fenikas]

I am not using Veeam Backup for AWS. It is normal veeam backup and replication and I setup a repository with AWS S3 bucket.

[nielsengelen]

Can you clarify a bit more the configuration of your SOBR and backup job which causes the issue?

[Fenikas]

For our SOBR, we hold normal backs for 90 days on our local drives, then on day 90, it is sent to our AWS bucket. It stays in this bucket for 1 day and then deep archived. This seems to be affecting all the backup that older than 90 days.

There is archive tier and the capacity is set to 10 TB. It just fails when it hits the "Preparing Index" phase and I get the Rest API error.

[Gostev]

Maybe there are some native lifecycle rules set up on the bucket which are changing the class of some objects? We can't really troubleshoot this over forum posts, you should just continue working with support and ask them why the error is occurring.

By the way, please include the support case ID for this issue, as requested when you click New Topic.

[veremin]

Once the data is in my normal S3 bucket, after 2 days, it will be deep archived.

It stays in this bucket for 1 day and then deep archived.

Are you referring to backup server settings or AWS S3 ones?

In the latter case the situation is expected, as we do not support it:

Data in object storage bucket/container must be managed solely by Veeam Backup & Replication, including retention and data management. Enabling lifecycle rules is not supported, and may result in backup and restore failures.

Thanks!