Discussions specific to the VMware vSphere hypervisor
Post Reply
TestYourMight
Novice
Posts: 7
Liked: never
Joined: Apr 28, 2018 1:27 pm
Full Name: TestYourMight
Contact:

Local Web Service and SureBackup

Post by TestYourMight » Jun 14, 2018 2:24 pm

Hello, we have a local web service, now we need to restore and run it from backup to figure out some info. But we want do this via SureBackup using vLab to learn the technology. I made Virtual Lab (with isolated network, static mapping etc.), Application Group and SureBackup task. Now when im starting the task the VM turns online and everything ok, i can ping it (static mapped ip address) but when i try to get web access from browser (access ip from static mapping) im logging to original web service, not the restored one.

Original web service: 172.16.1.6
vLab proxy: 172.16.1.150
Masquarade network: 172.16.101.D
Static Mapping:
Isolated IP - 172.16.1.6
Access IP - 172.16.1.156 (that is the ip i used to get web access)

Web Service running on CentOS 6.9.

If more info needed - just ask.

Dima P.
Veeam Software
Posts: 8576
Liked: 634 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Local Web Service and SureBackup

Post by Dima P. » Jun 14, 2018 4:56 pm

Hello TestYourMight.

You should use the mapped IP address instead of production one. Check how to properly configure IP mapping here: Specify Static IP Mapping Rules and let us know if it helps. Cheers!

TestYourMight
Novice
Posts: 7
Liked: never
Joined: Apr 28, 2018 1:27 pm
Full Name: TestYourMight
Contact:

Re: Local Web Service and SureBackup

Post by TestYourMight » Jun 18, 2018 9:31 am

Looks like i did it all right.

Image

IP i used to get web access is specified with red rectangle.

TestYourMight
Novice
Posts: 7
Liked: never
Joined: Apr 28, 2018 1:27 pm
Full Name: TestYourMight
Contact:

Re: Local Web Service and SureBackup

Post by TestYourMight » Jun 19, 2018 1:25 pm

Solved the problem, but not perfectly.
Made another one ip forwarding in vLab settings, started SureBackup job and inserted new windows VM in the isolated network. This way i reached needed web access through the "inserted VM".
Our problem was caused by DNS.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 9 guests