Veeam B&R 12.1 - Huge improvement with Backup to NFS

[broth-itk]

Dear Veeam Team,

this message is not to report a problem but to give out a huge THANK YOU to all persons involved in working to improve the software.

We noticed that Veeam 12.1 fixes an annoying reliability issue with NFS backup repos.
In the past we had the problem of failing backups due to NFS write errors.

I have not seen the part in the release notes addressing NFS but since the upgrade to 12.1 all the intermittent problems are gone.
What have I missed?

All the best and keep up your great work.

Cheers,
Bernhard

[Gostev]

Thanks for sharing, Bernhard.

This was probably some environment-specific bug due to backup storage or networking peculiarities (or something along these lines). Every release fixes literally thousands of such "corner case" bugs and it is physically impossible to put everything in the What's New document. Only the most significant enhancements that affect all customers are mentioned there and even with that, it is already 24 pages long for 12.1

Truth be told, improving our software is always a collective effort. We cannot take full credit for this as Veeam R&D can never do this alone, in isolation. We already ship a software that is bug-free in our own QA labs. So any remaining bugs will only be understood and fixed if affected customers open support cases and let us investigate our products' erroneous behavior in their specific environments. Only then we can see and fix issues we don't see in our own labs, on the hardware we use.

Further, the more support cases are opened on issues with the same root cause, the faster the root cause will be fixed - as the number of support cases is the primary prioritization metric. So even if you ever see on the forum that someone has already reported an issue similar to the one you're experiencing, please don't skip on opening your own support case. Especially since having more data from different environments always helps us tremendously when they are working on a newly reported issue. As seeing similarities between affected environments gives our QA good hints on how to reproduce the issue internally, which is always the first step.