SINC_dmack
asked on
Windows backup on Server '12 HyperV parent returns error when backing up host component
We have a Windows Server '12 HyperV parent that is running bare metal Windows Backups of itself and of its HyperV children. The backups complete successfully except that they fail to backup the Host Component. The exact error message is:
Error in backup of C:\\ProgramData\\Microsoft
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-F
Component: Host Component
Caption : Host Component
Logical Path:
Error : 8078010D
Error Message : Enumeration of the files failed.
Detailed Error : 8007007B
Detailed Error Message : (null)
Backups are being performed to a local USB drive. All other components (bare metal, VHDs, etc) backup successfully.
Several months ago, I did a restore of a child's VHD to an "alternate location" so I could recover some files out of it. If I recall correctly, something broke as a result. I don't remember if the subsequent problem was that the VMs wouldn't restart properly or if they wouldn't back up. I remember that some file location had been altered as a result of me backing up to an alternate location, and that I had to correct a registry entry to fix the problem.
I suspect that the current problem backing up the Host Component is somehow tied to whatever fix I had to do several months ago. Unfortunately, I didn't document the problem or the solution, so I don't recall specifically what I did. I do recall that whatever I did fixed the immediate problem. Searching Google for assistance (even specifying experts-exchange.com) has proved fruitless.
Error in backup of C:\\ProgramData\\Microsoft
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-F
Component: Host Component
Caption : Host Component
Logical Path:
Error : 8078010D
Error Message : Enumeration of the files failed.
Detailed Error : 8007007B
Detailed Error Message : (null)
Backups are being performed to a local USB drive. All other components (bare metal, VHDs, etc) backup successfully.
Several months ago, I did a restore of a child's VHD to an "alternate location" so I could recover some files out of it. If I recall correctly, something broke as a result. I don't remember if the subsequent problem was that the VMs wouldn't restart properly or if they wouldn't back up. I remember that some file location had been altered as a result of me backing up to an alternate location, and that I had to correct a registry entry to fix the problem.
I suspect that the current problem backing up the Host Component is somehow tied to whatever fix I had to do several months ago. Unfortunately, I didn't document the problem or the solution, so I don't recall specifically what I did. I do recall that whatever I did fixed the immediate problem. Searching Google for assistance (even specifying experts-exchange.com) has proved fruitless.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ken
Sounds good. Yes, I try to backup any registry hives before making changes. I will check back to see how it went.
ASKER
Last night's backup completed successfully.
I Googled for "msxml://C:\\ProgramData\\
I don't know if this was the specific site that I found several months ago when experiencing my initial problem after a restoring a VHD to an alternate location, but I feel at least a little better knowing that it's at least possible since there is at least one site with the fix with double slashes. Thanks for your help, Ken!
I Googled for "msxml://C:\\ProgramData\\
I don't know if this was the specific site that I found several months ago when experiencing my initial problem after a restoring a VHD to an alternate location, but I feel at least a little better knowing that it's at least possible since there is at least one site with the fix with double slashes. Thanks for your help, Ken!
Glad you worked through it and thanks for posting your solution. Many times a simple comment makes you look at something a little different to find the right path. Might not even be the solution but gets you going. Take care.
ASKER
Ken's comment pointed me towards something that probably should have been apparent to me in the first place, and fortunately regedit on the affected server opened to the exact key that was causing the problem, making troubleshooting a lot simpler.