nmdange wrote:If you have not done so, check my list of all the hotfixes that are out there and get your Hyper-V and SOFS clusters up to date, along with firmware and drivers.
nmdange wrote:Did you engage Microsoft support on the issue? It's hard to guess what the cause might have been, but I doubt that it was Veeam. I've had my share of Hyper-V issues and they've always either been a bug fixed with a hotfix or an actual hardware issue.
foggy wrote:Without installing Veeam B&R components on SOFS nodes Veeam B&R will not be able to track changes. I'd suggest to open a case for a deeper investigation, since the original issue should not be related to Veeam B&R components.
niknaks456 wrote:can you tell me how you manged to fix your issue?
Phorward wrote:In the end we had to destroy the cluster to be able to attach the Virtual Disk and then set up the cluster again.
Users browsing this forum: No registered users and 1 guest