+17Using the bUseLatestVDDKVersionPath Additional Setting, I am looking to force the use of VDDK901 for the protection of multiple 8.0.3 environments.
Given that VMware claims that VDDK is N-2 backwards compatible, I am interested to understand if anyone has faced any issues when forcing the use of a later VDDK version, and whether there are any caveats I should be aware of?
The key you mentioned is primarily for environments where you want to ensure all proxies use the latest VDDK for security, bug fixes, or uniformity, but it should be used with caution and only when you are certain all your VMware environments are compatible with the latest VDDK. Official support matrix will probably never state backward compatibility to a previous major version! You will have to find it the hard way :P
https://documentation.commvault.com/11.46/software/protect_vmware_vsphere_vms.html
+17Thank you, Doctor.
Unfortunately, I have a very long list of vulnerable libraries looming over me, a lot of which reside in VDDK folders. The intent here is to standardise under a single version of VDDK, which has fewer vulnerabilities.
Initial testing seems promising, but I will test further before pushing it wider.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
