Comprehensive data protection for all workloads
Post Reply
filippoAdb
Influencer
Posts: 20
Liked: never
Joined: Apr 08, 2021 12:59 pm
Contact:

Two sites architecture for B&R

Post by filippoAdb »

I have been walking in circle for days and I cannot find a guideline to choose the right architecture.
Currently I have 2 sites (A and B) and each one has its B&R server with its local repository. According the 3-2-1 backup strategy I'm testing backup copy jobs to the remote repository.
I read it is better to have the B&R gateway on the same site of the repository, so on site A Veeam infrastructure I added a site B server with transport component.
Is it correct ?
Can I add to site A infrastructure the B&R server on site B and use its transport component to connect to site B repository ? To put in other words I would like to use transport component of another independent Veeam installation.

My initial idea was to have a centralized management using a single instance of B&R server on site A and put a proxy and gateway on site B for local backups.
Then I read this answer in another discussion:
Our recommended practice is to keep a single Veeam B&R instance on the DR site to ensure a seamless DRP in case of the primary site failure.
I have two primary sites and each of them should act as a DR for the other. Can you please compare the pro and cons of having a B&R server instance on each site ?

Question about license.
I'm moving from socket license for both server to a single licence for 50 VMs. Can I use this license in the 2 B&R server scenario ? Do I have to split into 2 parts ? On Veeam license site I only found the merge option, not the split one.
What about the Veeam B&R instance on the DR site ? If I use that instance only for disaster recovery is it covered by the same license for the main site or do I need another one ?

Thanks
Mildur
Product Manager
Posts: 8735
Liked: 2294 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Two sites architecture for B&R

Post by Mildur »

Hi Filippo
I have two primary sites and each of them should act as a DR for the other. Can you please compare the pro and cons of having a B&R server instance on each site ?
Pro:
Having a backup server on each site allows you to do more granular permissions regarding backup server management via the Veeam backup console. If you don't want to let teams from site a accessing backups on site b via the backup console, this is one option to control it.
Con:
- More maintenance effort when it comes to updating your backup infrastructure.
- More hardening effort, because you need to harden two backup infrastructure against malicious attacks
- More monitoring effort, because you need to monitor two different environments

Can I add to site A infrastructure the B&R server on site B and use its transport component to connect to site B repository ? To put in other words I would like to use transport component of another independent Veeam installation.
Yes, it's possible but not recommended. If you start sharing repository hardware between multiple backup server, you will need to be aware of some limitation:
- hardware resource consumption: One backup server does not know about the other one. Both will try to use every available CPU or Memory for themselves.
- Veeam Backup & Replication update level: If you update one backup server, you must immediately update the second backup server. Transport Service on the repository server must always have the same version as the backup server or jobs will fail.
- Hardened repository: A harden repository server cannot be shared between multiple backup server
- Tape server: A tape server cannot be shared between multiple backup server

To keep things more simple, I recommend to have a single backup server to manage both sites. If you need to configure granular restore permission, use the enterprise manager for your helpdesk teams and allow only access to specific VMs. You may keep a replacement backup server in a second location. If the first backup server fails, import the configuration backup and keep continuing with your backup and replication jobs managed from the second site.
Question about license.
I'm moving from socket license for both server to a single licence for 50 VMs. Can I use this license in the 2 B&R server scenario ? Do I have to split into 2 parts ? On Veeam license site I only found the merge option, not the split one.
What about the Veeam B&R instance on the DR site ? If I use that instance only for disaster recovery is it covered by the same license for the main site or do I need another one ?
Using multiple backup server with the same license is fully supported. But you need to deploy our Enterprise Manager, install your VUL license and add all backup server. The enterprise manager will manage your license consumption between all backup server.

A DR/replacement server doesn't require a license for recovery sessions. As long there is no active backup or replica job, a license is not required. But you may add it to the same enterprise manager, to be prepared in case the DR server will be your new production server after a configuration restore.

Best,
Fabian
Product Management Analyst @ Veeam Software
Post Reply

Who is online

Users browsing this forum: Semrush [Bot] and 97 guests