Backup of vbo controller server with vaw

[Bjoern_ch]

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

[Mildur]

Hi Bjoern,

As discussed in our emails, I reached out to support management and asked them to continue with the case.
But I am still discussing our support statement regarding Veeam Agent protecting the VB365 machine when VCC is installed.

I’ll keep you updated.

Best,
Fabian

[Bjoern_ch]

Thanks a lot Fabian. I appreciate your effort on this.

[Mildur]

Hi Bjoern,

Good to see the case is progressing.

Veeam Agent for Windows (VAW) on a V365/VCC server: This is generally supported, but Support may ask you to remove it if it causes issues (e.g., "a VAW snapshot interfering with backup server tasks like tenant replication"). In your setup — since I assume Veeam Cloud Connect is only used for VB365 Self-Service Restore via the Explorers — we don’t expect interference.

Important: Always use a standalone agent for this scenario. An agent managed by another backup server can break the Data Mover Service on the Veeam Cloud Connect server. Based on the case notes, you are already using the standalone agent.

We’ve updated the v13 Help Center and removed the old “do not install VAW on the backup server” statement. A strict “Do Not Install” rule applies only to Linux infrastructure components and Veeam Agent for Linux (VAL) due to package conflicts.

After v13.1, we plan additional testing for this scenario, and I’ll push again for native configuration backup support.

Best,
Fabian