-
- Influencer
- Posts: 13
- Liked: 2 times
- Joined: Nov 22, 2016 12:51 pm
- Full Name: Thomas K
- Contact:
Accessing Production from Virtual Lab
Hi,
we need access to our production network of our Veeam Virtual Lab for licensing of an appliance.
Outgoing NAT would be sufficient to reach the license server in the production network.
Any chance to adjust/modify the Veeam proxy appliance without any workaround like 2nd NIC directly into production or other routing appliance in Virtual Lab?
Thanks,
Thomas
we need access to our production network of our Veeam Virtual Lab for licensing of an appliance.
Outgoing NAT would be sufficient to reach the license server in the production network.
Any chance to adjust/modify the Veeam proxy appliance without any workaround like 2nd NIC directly into production or other routing appliance in Virtual Lab?
Thanks,
Thomas
-
- VP, Product Management
- Posts: 7076
- Liked: 1510 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Accessing Production from Virtual Lab
No, the whole point of the Virtual Lab is to not let it communicate to your production environment.
The only way of communication is to use the Proxy Forwarder for Web Traffic (need internet proxy configuration in the lab VMs). This is for example helpful if you need windows update to work for your testings.
The only idea that I have additionally is to backup your licensing server with the Agent or VM processing. Or install a second one that is only connected to the virtual lab.
Maybe please share what kind of Software it is, maybe others here found a solution.
The only way of communication is to use the Proxy Forwarder for Web Traffic (need internet proxy configuration in the lab VMs). This is for example helpful if you need windows update to work for your testings.
The only idea that I have additionally is to backup your licensing server with the Agent or VM processing. Or install a second one that is only connected to the virtual lab.
Maybe please share what kind of Software it is, maybe others here found a solution.
-
- Influencer
- Posts: 13
- Liked: 2 times
- Joined: Nov 22, 2016 12:51 pm
- Full Name: Thomas K
- Contact:
Re: Accessing Production from Virtual Lab
Thanks for the feedback,
its a FortiManager doing the licensing for a virtual FortiGate. The ForitManager "plays" the proxy to the internet for activation.
So we may go the route with an second NIC on the Virtual Lab VM to get them in contact.
its a FortiManager doing the licensing for a virtual FortiGate. The ForitManager "plays" the proxy to the internet for activation.
So we may go the route with an second NIC on the Virtual Lab VM to get them in contact.
-
- VP, Product Management
- Posts: 7076
- Liked: 1510 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Accessing Production from Virtual Lab
I think you could do the following. Use the FortManager (as I understood Software system) as VM. Back it up and place it in a Application Group for the SureBackup Job (that way it is started upfront).
Use a pre script to configure the FortiManager with the Virtual Lab Internet Proxy. That way the Proxy can communicate with the internet.
It looks way more simple and clean and do not break the sandbox security.
https://www.veeam.com/kb1165
Use a pre script to configure the FortiManager with the Virtual Lab Internet Proxy. That way the Proxy can communicate with the internet.
It looks way more simple and clean and do not break the sandbox security.
https://www.veeam.com/kb1165
-
- Influencer
- Posts: 13
- Liked: 2 times
- Joined: Nov 22, 2016 12:51 pm
- Full Name: Thomas K
- Contact:
Re: Accessing Production from Virtual Lab
Great, then we will go that direction.
Who is online
Users browsing this forum: No registered users and 17 guests