Unable to storage migrate Instant ON VMs

[$username]

Case #03606082

Hi All,

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?

[HannesK]

Hello,
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

Best regards,
Hannes

[$username]

Correct, Storage vMotion using the migrate to production button. Normal vMotion works fine.

Thanks! I will read those.

[Andreas Neufert]

vMotion traffic is handeled by VMware and the storage connections. We just trigger the action within vcenter.

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.