Replication - same subnet at main & DR site, no L2, routing table change?

[TonioRoffo]

Hello,

I want to check if anyone is working with this scenario (or similar)

MAIN site:
All servers to be replicated in seperate subnet (10.10.10.0/24) - other devices at main site in other subnets, L3 routing defined in a switch
Clients, printers, etc in other VLAN/subnet on this site
Vmware/Veeam in a seperate VLAN/Subnet

DR site:
VM's ready in same subnet as abive in a seperate VLAN, isolated from the network in a VLAN without routing present
Veeam proxy(?) in seperate VLAN/Subnet. This subnet visible from the main site vmware/Veeam subnet

In case of failover:
* Change routing to 10.10.10.0/24 in the main switch so it gets sent over the WAN (VPN) link, change routing back to the MAIN site client VLAN
* Failover the machines

Is this scenario possible? Anything I need to think about or design? I want to avoid changing IP addresses and avoid having to create a L2 domain over WAN, as this introduces its own set of nightmares.
I am aware that this setup causes an all or nothing approach, either main or DR server site is active, no partial failovers.

Thanks.

[HannesK]

Hello,
having the same L2 network in a different site without routing is a valid design.

I just don't fully understand your failover scenario. If the MAIN site goes down, then the switch / router is also down. So 10.10.10.0/24 needs to be configured on a switch / router in DR site.

Best regards,
Hannes