- Veeam ProPartner
- Posts: 67
- Liked: 6 times
- Joined: Dec 09, 2014 4:28 pm
- Full Name: Gary Busey
We currently have an interesting situation and wondering how others have handled it, or ideas on how to solve this.
We recently configured our environment for Long Distance vMotion, for our config we used a VRF for security, and made it so it couldn't be routed to or from.
Obviously this seems to be causing some issues with our Veeam config as it isn't in that VRF'd network.
Is there a way I can configure our Proxy and Veeam to be dual homed and send vMotion traffic over a specific network?
- Veeam Software
- Posts: 4044
- Liked: 496 times
- Joined: Sep 01, 2014 11:46 am
- Location: Austria
just to clarify: you are talking about storage VMotion ("migrate to production" button in Veeam) for instant VM recovery - Correct? Or is it about "normal" vMotion between two ESX hosts?
The proxy is not involved in instant VM recovery process. The vPower NFS server is running on the mount server (usually the repository).
Search for vPower in the port list to see the relevant connections.
You can work with dual-homed networks, but I don't recommend it for its complexity (without real benefit). See preferred networks settings
- Veeam Software
- Posts: 3834
- Liked: 687 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
For the NFS connection traffic. We get all IPs from the Mount Server that runs the vPOWER NFS and try them to connect from the ESXi that you have selected. The first one that got a NFS connection we will use to mount the VM. For this there is no Veeam preffered network setting usable.
Users browsing this forum: Baidu [Spider], Bing [Bot] and 19 guests