Currently having some fun trying to do a test restore of a 2012 R2 physical server to a Hyper-V VM.
Have followed various guides, installed the VM from the ISO, basic Windows install.
Same hostname, IP.
Issued a new NB cert to the machine during client install, all NB connectivity seems fine.
No problems restoring the C: drive contents to the target, but then when it comes to restoring the System State I find that there is no NB connection to the target anymore, so unable to restore the System State.
Is there a way of doing this without BMR, or is that not supported for 2012 R2 and later?
Or are non-BMR system restores only supported to the original/identical hardware? (something I don't have access to in my test environment, hence the attemp to restore to a VM and try to resolve any issues thereafter).
Should I attempt to restore the System State before restoring the C: drive instead? I was always under the impression that the System State restore is needed to ensure the system configuration is correct, i.e. services, registry etc.
Page 162 of this guide appears to suggest I should be able to restore the system files and entire C: drive - so presume it is still possible? - https://www.veritas.com/content/support/en_US/doc/15179611-129887844-1
8 Use the NetBackup Backup, Archive, and Restore interface to restore the
system files and user files to the client system.
For example, if all files are on the C drive, restoring that drive restores the entire
As @Dollypee suggested, NetBackup BMR should be able to do what you need. BMR is designed to help migrate across hardware differences, and yes, your physical W2012R2 client is technically different hardware to a Hyper-V VM.
You could always try this:
How to use NetBackup to perform a complete restore of Windows Server 2008 R2 and above without IDR or BMR
...but note that the more different the source and target hardware is, the less likely a manual overlay method is to work.
Can you not take another backup, but this time BMR aware, of the original physical server?
Thanks sdo, it's looking like BMR is the way forward on this one.
I did try another restore but this time did the C: and System State in the same job, the result was a an unbootable system which ended up at the usual Windows troubleshooting blue screen - even bootrec.exe was not able to find a local Windows install to rebuild the BCD, so a dead end there really.
Is BMR now included by default in the Standard NB Client for free? - it used to be an additional licence in the past from memory.
Is that tick box all that is needed for this, or do we have to implement the rest of the BMR infrastructure (e.g. Boot Server etc.) as we currently do not have any BMR configuration in our live environment currently.