• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 255
  • Last Modified:

Veeam Istant Recovery in a host with different subnet

Same building, different departments with different WAN Connections.

Network 1 with a fortigate UTM

lan:192.168.200.x
Wan: x.x.x.x
vlan1 interface: 172.10.70.1

vlan1 interface provides necessary routing through a static route between 192.168.200.x and 137.0.0.x lans in order to achieve connection from veeam backup server to 137.0.0.x host.


host 1 vmware

1 dc
1 SMB

host 2 vmware

1 SQL Server DB APP

host 3 vmware

1 Veeam Backup Server

Backup REPO is in the 192.168.200.x network


Network 2 with a fortigate UTM

lan:137.0.0.x
Wan: x.x.x.x
vlan1 interface: 172.10.70.2

vlan1 interface provides necessary routing through a static route between 192.168.200.x and 137.0.0.x lans in order to achieve connection from veeam backup server to 137.0.0.x host.

host 4 vmware

1 dc
1 SMB
1 SQL Server DB APP

Scenario

We save all vm backups in the Veeam Backup Server in the 192.168.200.x network.

IF host 4 vmware goes in fault?
How could I perform a VM istant recovery for example in the host 1, host 2 or host 3 just to let employers continues to work?

All the other hosts are in the Network 1 (ip class 192.168.200.x), but VMs interested in restore in thi scenario have an IP class 137.0.0.x.

Thanks in advance guys!
0
Alessandro Scafaria
Asked:
Alessandro Scafaria
  • 3
  • 2
1 Solution
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
For any kind of site recovery service where we have a live backup in a different data centre the VMs would need to be tweaked for the site recovery's subnet. Once that is done with the requisite reboots they are live on that subnet.

Veeam has a sandbox feature. You could fire them all up in the sandbox, run through the IP changes needed, and verify that they all behave as expected. To further that test you could shut down the production VM and drop the restored VM onto the site recovery subnet to see how things behave from production to site recovery VM.

Other than perhaps the WAN limitation, and possibly the Line-of-Business app(s) itself things should run as expected.
0
 
Alessandro ScafariaAuthor Commented:
Hi guys,

I looked deeply into this.....Veeam doesn't provide a re-ip mapping when performing a VM Instant Recovery (only in case of replica).

The only way to resolve the issue is to connect "directly" the host using a VMware Distributed Switch. Once you use a physical nic as an uplink for this new VM Network, you may restore the VM directly without any changes.

If someone wants some other explanations, do not hesitate!
0
 
Alessandro ScafariaAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for tr4ding's comment #a40616898

for the following reason:

I tested the solution in person in a lab environment.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
I'm not sure why my answer, which is directly in line with yours, does not deserve at least some points?
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Thanks for that. :)
0

Featured Post

Microsoft Certification Exam 74-409

VeeamĀ® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now