VO365 Backup Copy Repository Limitations

[Matt.Sharpe]

Can anyone confirm why Veeam have restricted the backup copy target(s) to archive tier object storage only?

"You can use only backup repositories extended with the Azure Blob Storage Archive access tier, Amazon S3 Glacier or Amazon S3 Glacier Deep Archive storage as a target for backup copy jobs."

Doesn't make sense considering the access method is the same... something in the backend or way it stores the structure that's different?

[HannesK]

Hello,
the tiers are different from a cost model. So we treat them differently. Same protocol though, but different mechanisms in the background.

The goal is to save costs for customers. Glacier / Azure archive are the cheapest option to achieve that goal.

Best regards,
Hannes

[Matt.Sharpe]

That's fine for wanting to save customers money, however what about customers or providers that want to utilize their own object storage. You should make it available for people to have the option of what object storage to use and not restrict/force them down the public cloud archive storage route.

Some companies don't want to use public cloud, but this feature is forcing their hand...

[RomanK]

Hello Matt,

Unfortunately, we cannot share any ETA, but it's planned for future versions to support additional types of object storage.

Thanks

[HannesK]

so it is a feature request to support S3 instead of wanting to know why we only support Archive tier / Glacier?

yes, that request makes sense and is answered by my colleague.

[Zew]

Please support local storage (Block storage).

[HannesK]

block storage / Jet Database does not scale. Object storage is the way to go. Please don't expect any investment in Jet Database / block storage.

[Mike Resseler]

To add to this topic, we are planning/ working on supporting backup copy from ANY object storage to ANY object storage (so even cloud object storage to on-prem S3 or on-prem S3 to cloud and so on...)

[Zew]

block storage / Jet Database does not scale.

I'd like to have more of an explanation on what you exactly mean by this.

Why can't I just point to my main job, and point to another backup repo right in VB365, just as much as creating a backup copy job in VBR?

[HannesK]

that means, a few hundred users users usually work, but once you scale to thousands of users, the JetDatabase comes to its limits. That's why our focus is object storage.

I heard even from a small customer, that they just installed MinIO on Windows. It saved them disk space and performance (I don't have all details on the implementation, they just told me at an event that they were positively surprised)