The objective was to see of a Bare Metal restore would work to a new RAID 5 volume on the same machine.
The idea being if the C drive and BCD got messed up on the primary system RAID 5 virtual drive, creating another virtual drive with 3 more physical drives,
I should be able to restore the Veeam Backup.
The restore works, but the machine will not boot properly, not matter what I do.
After restoration, even with only one bootable RAID array, it always goes into Windows 2012 Repair mode, as the BCD is messed up.
I spent an entire day trying to understand what was going on, and both bootrec and bcdboot would not repair.
These are MBR volumes, and it appears that with multiple volumes present, VEB always want to restore to the original volume, even if I tell it to manually remap
to the new volume I created. I did this several times, and it always failed to make my new C drive, the boot volume, and instead booted from the original C drive volume.
I deleted all volumes from both raid arrays, and restored using VEB, and again it would always boot into repair.
I gave up, and restored using an image of System and C created with DiskImage from Lsoft, which works well on MBR, but not GPT.
After I did that, the system booted normally.
I created a new VEB. and will restore it to a new raid volume, after deleting the current one.
The objective again, is not to restore to the same RAID volume (that's easy), as that may not be possible in an equipment failure situation.
Will keep you posted.