Resolved it finally. The fix to the BMRUI error running from the WS 2008 R2 install disks was to copy the WindowsBackupImage folder to a smaller disk. The smaller disk size may or may not matter, original was 4TB containing daily backups, smaller was 750GB.
Note that the "System Volume Information" was NOT copied as one of the severe time-sinks was taking ~1hr to scan through all the backups before failing (WS 2008 R2 DVD) or suggesting the most recent (WS 2012 R2 DVD), which of course is the one I wanted in
the first place.
The restore happened, and the system tried to boot (initial WS 2008 R2 boot screen with right-scrolling green dots), but then restarted. On next reboot, it reported that system had failed to start and said that a needed device was missing; didn't report
WHAT device, not really helpful. Some forum entries said using BOOTREC was needed, however BOOTREC /ScanOS reported that it couldn't find a Windows Installation, even though Windows had booted far enough to show the logo.
Other forums suggested it was a UEFI/BIOS boot device issue, and considering that the original goal for this system was to replace a failing RAID array with new drives, that made sense. Reset UEFI/BIOS with "Load Optimized Defaults" setting. After a little
re-arranging of SATA cables to get the new drives onto what the BIOS then considered the first bootable SATA ports <drum roll> the system booted all the way to logon, reported it needed to be restarted because of new hardware, and on next reboot everything
was running as before the adventure began.
Here's the summary for others that may encounter this issue:
* BMRUI.EXE error from WS 2008 R2 DVD -- first indication of a problem, occurred after ~1hr scanning through stored backups
* Tried WS 2012 R2 DVD, which successfully found the desired backup (relief, and indication that Microsoft had fixed the bug I was experiencing), but it refused to do the restore since the backup was for a previous OS.
* Copied latest backup -- and it alone, no previous backups stored in System Volume Information -- from 4TB to 750GB drive. Unsure if drive size, or fewer backups to scan through that solved this issue. But I wasn't going to modify the original 4TB drive's
info in any way that would damage the safety net, so copying was the only perceived choice.
* Now the scan for backups was almost instantaneous, and the restore occurred without an error, system automatically restarted.
* Initial start-up screen was encouraging, but didn't get past right-scrolling dots before it restarted.
* Missing device reported.
* BOOTREC tried. UEFI/BIOS reset to defaults, drive cabling rearranged to make boot drive one of the first "seen" by BIOS.
* Success. Duration, 3 days, Sat-Mon.
Suggestions for Microsoft:
* Procedures that are not encountered frequently by users of your product need COPIOUS error and status reporting to help troubleshoot problems. This includes problems at OS boot and bare metal restore. Don't listen to the marketing-types who don't want
to "overwhelm the end-user". You can put up the pretty logo and scrolling dots, but immediately drop to a simple text display of what happened when problems are detected. Linux distributions aren't pretty when they start, but all the scrolling stuff goes
away quick when there are no problems.
* A null pointer. Really? Referencing memory location 0x00000000 is sophomoric, or at best expected in unreleased, untested code. Granted things may have changed significantly since the DVD was created as this is the nature of the technology world, but
see next entry.
* WS 2008 R2 post-release has seen big changes in available hardware. As stated earlier, don't know if it was drive size or number of saved backups that caused the install DVD's BMRUI.EXE error. But obviously MS fixed the problem by the time of the WS
2012 R2 DVD. Need to either provide updated restore DVD ISO for released & supported OSes, or allow the later OS versions DVD to restore previous OS backups. You can't leave your existing customers without a safety net, just like you can't make significant
user interface changes that alienate your installed base (Vista fixed in 7, 8 fixed partially in 8.1 and 10). I realize licensing and piracy are big issues, but they are taken care of during business hours, not when the end-user is trying to get things restored
outside of business hours in order to make sure everything is ready to run when the business opens Monday morning. Some procedures like backup restoration have to be free of the licensing concerns, and let the activation, Windows Updates, or other procedures
handle them. At the very least, the WS 2012 DVD could have said, "This is from a previous OS, or you sure?". That way, you won't have to update previous release's installation disks.