@JaySt to be clear we (Veeam) are waiting on a fix from Nutanix. They *may* be sending us a different and more appropriate HTTP status code in the fixed version so we need to be able to handle the legacy or updated scenario and since we will likely ship our v6.0 plugin prior to the Nutanix fix are preparing this release to handle either case. We did of course scope a workaround effort but it was impractical.
Statistics: Posted by ronnmartin61 — Jul 19, 2024 4:16 pm






