Unsolved
This post is more than 5 years old
3 Posts
0
822
August 13th, 2014 02:00
Recovering a Virtual Client (Hyper-V) with BMR
Has anyone had any success recovering a virtual Hyper-V client via BMR?
In this scenario I'm not using NMM and treating the Hyper-V client as a seperate entity.
Our environment in primarily VMWare and we're able to use the same process successfully however when recovering the Hyper-V virtual client we get the Windows Server 2012 BSOD stating a Critical Process has died and then continues to the Windows Boot Manager with:
Status: 0xc000000f
Info: A required device isn't connected or can't be accessed.
I've tried a few procedures where I boot from CD and try to fix the boot blk which looks like it works but final command fails as it can't find any bootable device.
There seems to be very little info regarding this situation as it's primarily dominated by talk about NMM I can't find anything to say it's unsupported either so will soldier on for a bit longer.
Some details:
Client: NW8.1.1 on Windows Server 2012 R2 (Hyper-V Gen2)
Host: Windows Server 2012 R2
NetWorker Server: 8.1.1 on Windows Server 2012 R2
Thanks in advance
Andrew
crazyrov
6 Operator
•
1.3K Posts
0
August 13th, 2014 03:00
Hi Andrew,
To summarize you have trouble getting the virtual client boot up using the NW 8.1 BMR iso, correct ? Also, can you provide the exact name of the BMR ISO that you are using.
AndrewK2
3 Posts
0
August 13th, 2014 04:00
Hi there,
Sorry for the confusion, the BMR side of things is fine. I can boot from the iso, fill in the details and recover as per normal.
Unfortunately the client is unable to boot after I've recovered the data.
Just in case it helps the name of the iso is NetWorker_8.1.1.280_Windows_BMR_Wizard_x64_WinPE_50.iso
Regards
Andrew
crazyrov
6 Operator
•
1.3K Posts
0
August 13th, 2014 22:00
Then it might be that the original server from where the backup was done does not have the same disk drivers that are required by your current VM. You will have to compare both the configurations and ensure everything matches.
AndrewK2
3 Posts
0
August 15th, 2014 01:00
Hi crazyrov,
I'll look into the configuration. I didn't make any changes to the virtual machine and simply recovered over it as if it were a bit of tin.
I have to confess that my Hyper-V knowledge is limited so I'm hoping I'm not making a "school boy" error.
I'm still curious to know if anyone has had any success recovering a hyper-v client this way.
Thanks
Andrew