set storage class in S3-storage

[dw432948jkk]

How do I set a different storage class to store in S3, Azure or GCS? The agent always uses the standard storage class, which is usually the most expensive variant of cloud storage.

Do you really have to create your own XML files with the veeam agent configurator?

Wouldn't it be easier for customers if veeam could offer this in the agent gui?

[HannesK]

Hello,
there is no option in the standalone agent. If you have an agent, that is managed by Veeam Backup & Replication (VBR), then VBR will manage that.

which is usually the most expensive variant of cloud storage.

that depends on the retention. For short retentions, the standard class is usually the cheapest.

On Azure, one can set the storage class at container level if needed.

Wouldn't it be easier for customers if veeam could offer this in the agent gui?

easier yes, but the question is, whether that choice would be good for end-users and whether they have the knowledge to decide. The Backup administrator can do it it via VBR

Best regards,
Hannes
PS: if someone is looking for the cheapest option, then Wasabi, Backblaze or others would be much easier than trying to optimize costs with the "big three"

[dw432948jkk]

We tried this on Google cloud storage: even if you set a storage class there at the container level, e.g. archive, the veeam agent saves the files there in the standard class.

[dw432948jkk]

if someone is looking for the cheapest option, then Wasabi, Backblaze or others would be much easier than trying to optimize costs with the "big three"

Of course we knew that. However, it should be stored immutable in the archive on Google cloud storage as a backup of the backup and "data grave", which actually only needs to be used in extreme emergencies. And in archive storage only, the big three are cheaper than Wasabi and Backblaze.

[HannesK]

Google cloud storage does not support object lock. So there won't be immutability with Google.

[dw432948jkk]

Of course they do:

https://i.im.ge/2023/03/21/Dfyraa.gcs.png

[HannesK]

I'm not an expert for Google, but that looks like object versioning. Not object lock. Maybe that is their native API. Google has S3 compatible and a native API to their object storage. Veeam is using the S3 API.

If they had S3 object lock, then they would be in the Veeam Ready database listed as compatible with object lock