Veeam 12 direct‑to‑object storage vs SOBR

[villapla]

Hi

We are about to deploy VBR 12 for VMware vSphere and I'm wondering about the advantages of SBR vs direct‑to‑object storage.

AFAIK our current Standard perpetual socket based license supports direct‑to‑object storage with VBR 12 and we would need to upgrade to Enterprise/Enterprise Plus in order to use SOBR.

We are planning to keep our current schema of two local encrypted copies (via Backup Copy Job) on different Linux Hardened Immutable repositories with XFS fast cloning but adding a third encrypted immutable fast cloned copy (via Backup Copy Job) to Azure Blob Storage.

So the question is, it's realistic to use direct‑to‑object storage or we should definitely go to SOBR?

Thanks in advance,
Juanjo

[Mildur]

Hi Juanjo

AFAIK our current Standard perpetual socket based license supports direct‑to‑object storage with VBR 12

Must be a Bug. Standard sockets don't allow backup to object storage. Only restore from Object Storage.
There was a know bug with the Standard rental license, which we have solved in our first cumulative patch.

If you want to use SOBR or direct backup to object storage you have to upgrade your license.
https://www.veeam.com/veeam_data_platfo ... son_ds.pdf (Page 7 - ENHANCED Object storage)

So the question is, it's realistic to use direct‑to‑object storage or we should definitely go to SOBR?

Both methods are ok and have their benefits. Some examples:

SOBR:
- SOBR requires less jobs to manage
- Archive Tier still requires a SOBR

Direct Copy to object storage:
- more flexibility in choosing your retention

Best,
Fabian

[villapla]

Hi Fabian,

Thanks for your fast response.

Regarding to the standard socket license features, it was my mistake, the document you linked is absolutely clear about this.

Best regards,
Juanjo

[tyler.jurgens]

I've been doing a significant amount of testing with Direct to Object storage lately.

In all honesty I'm failing to see much benefit to using SOBR offloading, with the exception of the Archive Tier.

Pros of Direct to Object:
Save on complexity of SOBR. If you don't have a SOBR already, setting one up just to use Object Storage may not be worth it. SOBRs are great, but they come with their own challenges.
Manage your jobs as you always have been. You need to do almost nothing different or special to go Direct to Object Storage. You can create a Object Storage Repo and use it like you've used every other repository in the past.
As with Managing your jobs, monitoring and troubleshooting is very similar to any other repo you've always been using.

Cons of Direct to Object:
If you truly want that additional Archive Tier, you'll have to create additional backup copy jobs. More jobs to manage.

[Gostev]

Here are additional pros and cons > Backup Copy to Object Storage vs. Scale-Out Backup Repository Copy Mode