Is it possible to add a Veeam hardened Linux repository to two VBR servers ?

[massimiliano.rizzi]

Hello Community and good day,

please consider the scenario below from a Veeam perspective:

==================================================
- a physical Windows server acting as the VBR server (with Socket License used to backup VM workloads) and the primary backup repository
- a physical Linux server acting as the secondary Veeam hardened Linux repository (currently used to store backup copies of VM backups)
- a dedicated Windows server VM acting as a separate VBR server (with Veeam Universal License used to centralize configuration and management of Veeam Agent backup jobs). The physical Windows server above is currently added to the console of the VBR server VM as well in order to serve as the primary backup repository for Veeam Agent backups (both VBR servers are upgraded timely close to each other every time in order to maintain the same version of the Veeam datamover)
==================================================

Our Customer would like to add the Veeam hardened Linux repository to the console of the VBR server VM as well in order to store additional copies of Veeam Agent backup jobs.

Is this scenario supported ?

Thank you in advance for taking the time to read my post. Any suggestions and thoughts will be greatly appreciated.

Kind Regards,

M.

[Mildur]

Hi Massimiliano

No, it‘s not possible. But why are you not using a single vbr server for vms and agents instead?
You can merge the socket and the VUL license to use it on a single vbr server. Merging License

Limitations for Hardened Repos

The hardened repository cannot be shared between different Veeam Backup & Replication servers.

[massimiliano.rizzi]

Hi there Mildur ! Thank you for taking the time to reply my post.

Being able to use a single VBR server would be great, however on a previous call with our Veeam representative we were explicitly told it is not possible to merge Veeam Backup Essentials Socket licenses and Veeam Universal Licenses in order to use them within a single VBR server.

If merging is actually possible we are all set and we can get rid of the separate VBR server used for management of Veeam Agent backup jobs as well.

Kind Regards,

M.

[Mildur]

Your welcome.
Yes, you are correct. With essentials, merging is not possible. You would need to convert them to a VUL.

[veremin]

You might want to reach your sales representative to discuss license migration options, chances are there is an opportunity to leave socket license behind in favor of single VUL license that covers both virtual and physical workloads. Thanks!

[Jonyrock]

The hardened repository cannot be shared between different Veeam Backup & Replication servers.

What If I lose the one VBR server (VBR1) connected to the Linux hardened repo (linuxrepo1) and don't have time to rebuild it, but I have another VBR (VBR2) server up and running, backing up other workloads. Can I connect the Linux server (linuxrepo1) to the VBR (VBR2) server, then create a new hardened repo by specifying the filesystem path, then scan the repo so that data appears under disk import, and then perform all restore or backup operations after mapping? I hope this can be achieved.

[Mildur]

Hi Jony

Yes, that‘s perfectly fine and supported.
Connect the hardened repository to VBR2 and import the backups.

Thanks
Fabian

[Jonyrock]

Many thanks for your reply