Access SureBackup vm using original ip

[KeiichiKun]

Hi all,
I've a SureBackup job with one RedHat vm, for example named REDHAT01 with ip 10.200.42.61

This is my virtual lab configuration:

Folder name: VLH

Production network: prod_1
Ip: 10.200.42.22
Mask: 255.255.0.0
Default gw: 10.200.0.90
Dns: 10.200.80.3

Network options:
Isolated network: VLH prod_1
Masquerade ip: 10.240.0.0 (/16 vNic1)
Appliace Ip: 10.200.0.90 (as the default gw)
DHCP: enabled

Network mapping:
prod_1 --> VLH prod_1

I can ping the virtual appliance with ip 10.240.42.22 and 10.200.42.22
Everything is ok, i can ping and access the vm using masquerade ip 10.240.42.61

Now, a colleague of mine asks me if he can connect his application (now using 10.200.42.61 as target ip) to the vm created by SureBackup if REDHAT01 is powered off.
I've tried using some static route passing through the virtual appliance but with no success. Any way to achieve this?

Thanks

[PTide]

Hi and welcome to the community!

If you want to make SureBackup VM accessible from the production there are other ways to achieve that.

Thanks.

[KeiichiKun]

Hi, thanks for your reply.
I've already followed that link but I don't think it can solve my problem.
Using static mapping I should use another ip address to access the vm behind the virtual appliance (for example, 10.200.42.61 is the original ip, 10.200.42.161 is access ip), but I can't do that, I must use the original ip because software configuration can't be modified.
Maybe I should add a routing rule inside the VA?
Thanks again

[tdewin]

So if I understood it correct, you want the VM to have the exact same IP as the production machine + you will shut down the original VM? In this case, why do you not just do an Instant VM recovery manually but do not restore to the original location (eg give it another name)?

[PTide]

In this case your production default gateway has to be aware that all packages that are targeted to the surebackup VM's (REDHAT) IP should be forwarded to the virtual appliance, not to the production REDHAT. Virtual appliance has to be able to redirect an inbound traffic from production to the surebackup VM and vice-versa. In other words you need to tweak NAT rules on your production network gateway and on the appliance.

Thanks

[KeiichiKun]

Yes, that's what I was thinking, I'll try to implement the routing
Thanks again

[KeiichiKun]

Hi,
If someone needs it, that's what I've done
1- add route on client ip like 10.200.42.61 255.255.255.255 10.200.42.22
2- add route on va like ip route add 10.200.42.61 dev eth1 (gateway interface)

Bye