Mike Resseler wrote:Hi Daniel,
I see your case is closed? Is that correct?
eainsworth wrote:Just migrated my Hyper-V cluster to 2016 over the weekend and ran into this issue with backing up Exchange 2010 on the upgraded cluster. We performed this upgrade hoping for better backup performance with the native 2016 RCT feature. Instead, we no longer have a working backup infrastructure. Has anyone upgraded their Veeam backup server to Windows 2016? Any different results?
Mike Resseler wrote:Ah, thanks Daniel, I was indeed looking at the old support case. Not too happy that the first support engineer wasn't very helpful. If you feel it is necessary, please escalate this. We take a lot of pride in our support department and our VP's running the different divisions are working always very hard to solve issues where the engineer didn't do what needs to be done.
I hope that you have better success with the new one, please escalate if necessary. We might need to get it to DEV team if it is locked at some point (although I hope not...)
Mike Resseler wrote:Daniel,
Just looked and it seems that you are still doing tests together with our support engineer. Please keep pushing . I'm hoping that support and dev are already working together now.
matt306 wrote:I've had the same issues with a cluster that's been rolling upgraded to 2016. My current workaround is to keep a single node with 2012R2 (paused) in the cluster as it causes Veeam to behave differently and backups succeed (albeit with no CBT). Obviously if you've already upgraded the functional level to 9, this isn't an option for you.
Users browsing this forum: No registered users and 1 guest