Home / server / Questions / 1001084
In Process
fcm
Asked: 2020-01-31 07:30:36 +0800 CST

Windows 2019 backup: bare metal restore

  • 772

I'm rehearsing a virtual machine bare metal restore.
Backups are taken daily and saved on a secure external server.
We are assuming a total disaster, so bad that no domain controller is available, so, I can't use System Center Virtual Machine Manager just the 'default' Hyper-v manager.

The recovery I'm trying to do is as follows:

  • Setup a new windows 2019 Server.
  • Add a working Hyper-V role.
  • Create a new virtual machine with the same original configuration.
  • On the new VM connect valid Windows 2019 CD/DVD ISO image.
  • Boot from the ISO image.
  • Select repair.
  • Do a System Image Recovery
  • on Windows cannot find a system Image Backup, I press Cancel, Next, Advanced and select Search for a System Image on the Network
  • Connect to the network (grab a coffee)

And here, I tried different options: to use a unprotected share, with or without '$' names, using ip address, with username/password: nothing seems to work. Always the same answer:

An internal error occurred. The following information might help you resolve the error:   
The network path was not found. (0x800070035)
disaster-recovery hyper-v-server-2016 windows-server-backup

1 Answers

  1. That sounds ridiculously complicated. Basically keep backups for a start config separately. So, after step 2 you restore the backups (dc etc.) and take it from there.

    • 0