vProxy version for 19.6.1

There is no mandatory link between the exact vproxy version released with a new NW version. The "NETWORKER ALL MODULES & FEATURES Simple Support Matrix" for NW19.4 until 19.6 states:

- Dell EMC vProxy: 4.3.0.x

So ANY 4.3.0.x vproxy version is supported, so you can use the fixed vproxy version released together with nw19.6.0.3. But I'll give you that normally a NW version released later would contain a higher vproxy version whereas nw19.6.0.1 was released one week after nw19.6.0.3, while the vproxy released together with nw19.6.0.3 is higher than the one released together with nw19.6.1.

Possibly there was a delay of nw19.6.1 causing this discrepancy, but as said no requirement whatsoever to have to use that exact version. Simply use the fixed vproxy-installer-4.3.0-20.ova from April 20th.

While for NW19.3 it states a much wider range:

- Dell EMC vProxy 4.0.0-x
- Dell EMC vProxy:4.2.0-x
- Dell EMC vProxy 4.1.0-x
- Dell EMC vProxy 4.3.0-x

So whenever a DSA or DTA states a version to be fixed, you simply take that higher vproxy version, which as said has no direct mandatory required link with the NW version it was released with. We prefer to separate the vproxy upgrades (or rather replacements as there is no upgrade method used as it is a complete redeployment) from the NW upgrades. Only when upgrading from nw9 to nw18.2 we had to do both as the old vproxy was not supported with nw18.2 (even though it proved even to be working when we had to use the lower vproxy version as the higher used a different snapshot quiescing method on vmware end (without stating anywhere in the documentation it was doing so, but due to an antivirus product preventing the vmware tools snapshot service to be installed on Windows VM's, the new quiescing method failed and reverted to non-qiesced snapshot due to which all vm's that had to use vmware tools pre-freeze and post-thaw commands to suspend the activity of a database no longer performed the quiescing).