Comprehensive data protection for all workloads
Post Reply
EmreD
Lurker
Posts: 1
Liked: never
Joined: Sep 29, 2025 11:49 am
Full Name: Emre Durudogan
Contact:

Azure Local - Replication between 2 different location

Post by EmreD »

Hello,
We are offering an Azure Local solution with HPE's validated nodes. The Customer has 2 different locations that have over 5ms latency between them. That is why they are unable to use Microsoft's RAC solution. We decided to use Veeam for replication purposes. For this use case, should the number of nodes in the Prod and DR locations be exactly the same? Is there such a rule? Or can we proceed with a solution like adding 6 nodes in Prod and 3 nodes in DR, as we always have? I heard this mentioned as an important note in a session I attended last year, but I can't find the source now. Since I can't find the exact same information, I need your help to confirm this.
In summary, due to budget constraints, our customer wants to place fewer nodes in the DR location and only replicate critical workloads there. Can this be done using the Azure Local solution? Or should it have the exact same number of nodes?

Many thanks
david.domask
Veeam Software
Posts: 3015
Liked: 700 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: Azure Local - Replication between 2 different location

Post by david.domask »

Hi EmreD,

For Veeam's replication, number of nodes is not super relevant, instead ensure that the target host(s) have necessary resources (CPU / RAM / storage) to host the replicas and to be usable should a failover be required.

Can you share which Microsoft Product you're talking about btw? Quick search doesn't really show anything.

Please check this KB carefully (including the additional links) for the considerations: https://www.veeam.com/kb4047
David Domask | Product Management: Principal Analyst
Post Reply

Who is online

Users browsing this forum: DaStivi, GenDev, Markush-VE, Matthias.Mehrtens and 16 guests