We use 3pars as our storage platform and run Veeam 9.5 update 1.
A previous version of the hp Firmware for the 3pars (version 3.2.2 mu3 ) broke the virtual copy backups used by Veeam because HP changed the method and security of communications to the 3par hence veeam could not call a virtual copy.
Does anyone know if 3.2.2 MU4 has the same issue or has it been fixed or has Veeam addressed this issue in updates and problem has gone away.
We stayed on MU2 instead of going to MU3, even though veeam wrote and compiled a DDL for us, the risk was too great because of our large environment but would like to go to MU4. Just can't find anything on this issue.