Discussions specific to the Microsoft Hyper-V hypervisor
Post Reply
Blue407
Enthusiast
Posts: 96
Liked: 12 times
Joined: Apr 12, 2016 2:14 pm
Full Name: Paul Thomas
Contact:

Server 2016, Veeam B&R 9.5: KB2058

Post by Blue407 » Aug 30, 2018 3:10 pm

Hey All

So we have the above setup, and are getting a Event error of 5125.

Further investigation has found this knowledge-base article: https://www.veeam.com/kb2058
Has anybody else experienced this and what did you do to solve it?

I have a daily job that creates a backup of the Host servers very early every morning. Is it this job that's creating the recovery media?
Just trying to understand this a bit more, so I can try and fix, or workaround it.

PS. This is only happening on one of my two Hyper-V Cluster nodes.

foggy
Veeam Software
Posts: 18251
Liked: 1558 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Server 2016, Veeam B&R 9.5: KB2058

Post by foggy » Aug 30, 2018 4:26 pm

Hi Paul, if you're backing up the host itself using Veeam Agent for Windows, then yes, it looks like it is the job that creates the recovery media.

Blue407
Enthusiast
Posts: 96
Liked: 12 times
Joined: Apr 12, 2016 2:14 pm
Full Name: Paul Thomas
Contact:

Re: Server 2016, Veeam B&R 9.5: KB2058

Post by Blue407 » Aug 31, 2018 7:27 am

Is there now a proper solution for this? This problem was discovered in 2015!

I do not understand why one of the two cluster members is giving this error yet the other isn;t? Both hosts are backed up using the same job (Veeam agent for Windows).

foggy
Veeam Software
Posts: 18251
Liked: 1558 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Server 2016, Veeam B&R 9.5: KB2058

Post by foggy » Aug 31, 2018 4:45 pm

Only one of them is the CSV owner. The available workaround is described in the KB article you've mentioned.

Post Reply

Who is online

Users browsing this forum: No registered users and 13 guests