2 issues prevent me from purchasing

[joloo]

So, I've always heard good things about Veeam backing up Hyper-V VMs. However, looking through the forum here, 2 things stick out:

#1
Support. How is the support recently?

#2
Now, this is the big one. This topic microsoft-hyper-v-f25/windows-server-20 ... 62112.html shows that there has been an ongoing issue for 4 years now that can potentially affect anyone. Veeam isn't cheap, and I don't want to spend such a significant amount of money knowing that at anytime, I could be hit by this bug... with basically no end in sight. At almost 750,000 views and years of non-action, that topic is extremely concerning.

I'm basically wanting to backup a few Hyper-V VMs with the paid subscription of Veeam. Can anyone give me some reassuring reasons that the above two points should not stop me from proceeding?

[sivein]

1) Support is pretty much OK. No worries
2) Please read in detail some of the post's under that topic and I think you will find that this is not a Veeam related problem....

[joloo]

2) Please read in detail some of the post's under that topic and I think you will find that this is not a Veeam related problem....

I have read through that topic. You and I have different definition of "related". I'm not saying that Veeam is the cause of the issue, but just the fact that using Veeam triggers the issue and/or this happens while using Veeam, by definition, makes this problem related to Veeam.

In the end, it doesn't really matter as long as the following 2 items are true:
This appears to be an issue that can potentially affect anyone that purchases Veeam to backup Hyper-V.
Veeam, although not at fault, cannot provide a resolution to this problem that can potentially affect any of it's customers.

[Andreas Neufert]

Not saying that it is good, but the Microsoft RCT issue can affect any backup product out there. In the mentioned forum thread, more and more customers from other backup solutions come together to share their findings and work with Microsoft on this.

You can use our managed agents (Agents in VMs) to avoid this issue completely. Microsoft is updating (Stephen Cole with the bold blue forum name) the community in the thread on their progress and they are searching for some customers that can reproduce the issue reliably to test their progress.