Hi veeam team,
I know there are many threads in this forum about this topic. I have read those. Most of those threads recommend using vbr (if available) or veeam agent to make a backup of the controller server. BP guide is similar: https://bp.veeam.com/vb365/guide/design ... h_vbr.html
As our VM is running on Openstack we cannot use vbr and opted for vaw instead.
Unfortunately, now the vaw team is refusing to support a problem I have with this agent backup (cannot change the destination from cloud repo to S3 repo).
Their argument is that we have vbr installed on top of our vbo/vbm. And backing up vbr with veeam agent is not supported they say:
https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13
But as we are a veeam backup for M365 service provider and need Cloud Connect we MUST do that. It is documented here: https://helpcenter.veeam.com/docs/vbo36 ... html?ver=8
If veeam really does not support this scenario there are huge implications: This would mean that veeam, as a backup vendor, is not capable of backing up their own vbo service provider environment. Or do I miss anything here?
Could you please clarify? Thanks.
Bjoern
Case # 08138263
-
Bjoern_ch
- Service Provider
- Posts: 101
- Liked: 33 times
- Joined: Sep 09, 2022 12:22 pm
- Full Name: Bjoern
- Location: Zurich
- Contact:
Who is online
Users browsing this forum: Google [Bot], Semrush [Bot] and 107 guests