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.
-
- Enthusiast
- Posts: 99
- Liked: 13 times
- Joined: Apr 12, 2016 2:14 pm
- Full Name: Paul Thomas
- Contact:
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Server 2016, Veeam B&R 9.5: KB2058
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.
-
- Enthusiast
- Posts: 99
- Liked: 13 times
- Joined: Apr 12, 2016 2:14 pm
- Full Name: Paul Thomas
- Contact:
Re: Server 2016, Veeam B&R 9.5: KB2058
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).
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).
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Server 2016, Veeam B&R 9.5: KB2058
Only one of them is the CSV owner. The available workaround is described in the KB article you've mentioned.
Who is online
Users browsing this forum: No registered users and 17 guests