Hi,
Disable or uninstall security software temporarily to check.
I consider that replace the backup drive and reconfigure a new backup. If the new backup fails then you have a problem on the server. If it doesn't it was the backup disk and you're done. Troubleshooting the server can be a chore. Check amount of free disk space on all the drives and start reading event logs.
You might need to look at dump to find out where the hang is. Procdump is a choice.
https://video2.skills-academy.com/en-us/sysinternals/downloads/procdump
Please remember to accept the answer if they help.
Best Regards,
Carl
'wbadmin start sysrecovery‘ stuck on Bare Metal Recovery stage started: Running a recovery operation for volume LOGS(F:)
I had a WSB for 2012R2(Hyper-V VM) with the following fixed volumes.
When I perform Bare Metal Restore on another blank host(another Hyper-V VM with three disk),
wbadmin start sysrecovery -version:08/27/2020-06:24 -backupTarget:"\?\Volume{67e9db52-e91d-11ea-a635-00155d060465}" -recreateDisks -restoreAllVolumes -quiet
Sometimes it can be restored successfully, sometimes it(wbadmin get status ) will stuck on 'Bare Metal Recovery stage started: Running a recovery operation for volume LOGS(F:)' and the command 'diskpart' stucked also,
, and the service VDS cannot be stopped.
1 answer
Sort by: Most helpful
-
Carl Fan 6,851 Reputation points
2020-08-31T09:58:50.83+00:00