Feature request: InverseVssProtocolOrder selectable PER job.

Discussions specific to VMware vSphere hypervisor

Feature request: InverseVssProtocolOrder selectable PER job.

Veeam Logoby olafurh » Fri Sep 09, 2016 1:55 pm


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.

Veeam Vanguard
Veeam Vanguard
Posts: 9
Liked: 13 times
Joined: Wed Oct 29, 2014 9:41 am
Location: Iceland
Full Name: Olafur Helgi Haraldsson

Re: Feature request: InverseVssProtocolOrder selectable PER

Veeam Logoby orb » Tue Nov 15, 2016 1:34 pm

+ 1

Posts: 23
Liked: 4 times
Joined: Fri Apr 01, 2016 5:36 pm
Full Name: Olivier Bonemme

Return to VMware vSphere

Who is online

Users browsing this forum: quintero and 31 guests