Hello Team
In V12 we add second network interface to Veeam Mount Server and restore tenant guest files. After that remove the network interface and secure the network.
In V13 we can not able to do it. Veeam not choose second ethernet adapter and connect vSphere Guest Interaction API and restore rate is 3 KB/s
How we can disable this behaviour? This is terrible.
-
mehmetistanbullu
- Service Provider
- Posts: 272
- Liked: 30 times
- Joined: Dec 14, 2015 8:20 pm
- Full Name: Mehmet Istanbullu
- Location: Türkiye
- Contact:
-
HannesK
- Product Manager
- Posts: 15798
- Liked: 3514 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Disable Restoring via vSphere Guest Interaction API
Hello,
VIX / vSphere Guest Interaction API is a fallback mechanism. If that comes into play, then restore via network failed. If the same setup worked in V12, then it should be investigated by support. Do you have a support case number?
Best regards
Hannes
VIX / vSphere Guest Interaction API is a fallback mechanism. If that comes into play, then restore via network failed. If the same setup worked in V12, then it should be investigated by support. Do you have a support case number?
Best regards
Hannes
-
mehmetistanbullu
- Service Provider
- Posts: 272
- Liked: 30 times
- Joined: Dec 14, 2015 8:20 pm
- Full Name: Mehmet Istanbullu
- Location: Türkiye
- Contact:
Re: Disable Restoring via vSphere Guest Interaction API
No, I didn't open a case to discuss this first, but I'll open one now.
Yes, it's a fallback mechanism. However, previously, it checked if there was another Ethernet card at the L2 level on the mount server. Example:
Veeam Server IP: 10.10.10.10
Backup Repository: 10.10.10.11
Mount Server: 10.10.10.12
Restored VM IP: 192.168.1.10 behind a different firewall
So I attach another virtual Ethernet adapter and IP address 192.168.1.11 to the mount server.
In this way, when Veeam was restoring a backup, it first checked its own network, then the other Ethernet adapter, and if it couldn't find that either, it would revert to VIX.
Now, however, this behavior has changed.
Yes, it's a fallback mechanism. However, previously, it checked if there was another Ethernet card at the L2 level on the mount server. Example:
Veeam Server IP: 10.10.10.10
Backup Repository: 10.10.10.11
Mount Server: 10.10.10.12
Restored VM IP: 192.168.1.10 behind a different firewall
So I attach another virtual Ethernet adapter and IP address 192.168.1.11 to the mount server.
In this way, when Veeam was restoring a backup, it first checked its own network, then the other Ethernet adapter, and if it couldn't find that either, it would revert to VIX.
Now, however, this behavior has changed.
VMCA v12
-
HannesK
- Product Manager
- Posts: 15798
- Liked: 3514 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Disable Restoring via vSphere Guest Interaction API
your description feels correct, and I cannot remember changes around that.
Who is online
Users browsing this forum: AdsBot [Google], Amazon [Bot] and 219 guests