Hi,
In a big environment, where you have mixed customers (all size and shapes) some times VMware VIX is not able to handle all the traffic it needs at the speed you need (restores and SQL transaction logs backups for example) .
It would be really beneficial to have the InverseVssProtocolOrder (the registry key) selectable per JOB so you could have the default traffic over VIX but select the few jobs you can open the network to use the network.
Having the InverseVssProtocolOrder = 0 (go first over the network and then failover to VIX) globally is not a good option because it adds "false" errors to the job run and adds extra time processing each VM.
olafurh
Veeam Vanguard
-
- Service Provider
- Posts: 25
- Liked: 16 times
- Joined: Oct 29, 2014 9:41 am
- Full Name: Olafur Helgi Haraldsson
- Location: Iceland
- Contact:
-
- Service Provider
- Posts: 126
- Liked: 27 times
- Joined: Apr 01, 2016 5:36 pm
- Full Name: Olivier
- Contact:
Who is online
Users browsing this forum: Google [Bot] and 79 guests