Unfortunately, it does not appear that any logs were created so I guess I had to explicitly ask for them during the process. I will attempt to recreate the problem next time I visit the location.

The whole idea of doing a bare metal restore from the cloud seems strange to me. In this case I had file and folder backups in the cloud and an image on local storage. I wanted to restore from a local backup. It does not seem that syncing to the cloud makes any sense unless you indicate that you want to restore from the cloud. It is just wasted time. Also, why not default to restore only for all backup locations. What is the use-case for doing anything other than a bare metal restore with a Boot USB?

In this case, I was attempting to restore to a new boot volume so this was not an emergency. I just thought it would be a good chance to test the process. I'm glad I did since there seem to be some problems that I would not want to discover during a real emergency restore. I gave up and used another tool to image the drive.

Adding PERCSAS2 has gotten me a step further. I can now see the RAID volumes in DISKPART. However, when I start the restore wizard, I get a message saying "Sychronization is in Progress. Please Wait." I have let this run for up to 10 minutes, but it never seems to complete. ANY THOUGHTS?

Matt, I created a new USB ISO and added PERCSAS2 from C:\Windows\System32\DriverStore\FileRepository in the "Path to Drivers" field. Now the PERCSAS2 drivers appear in boot.wim . I will not be able to try the restore for a few days. So I won't know if that solves the problem until then.

I could see having to do this if I was restoring to dissimilar hardware.

Matt, I am restoring to the same hardware. Shouldn't the boot USB build copy all the necessary drivers? I am trying to restore Server 2008R2 if that matters.

I browsed through the \sources\boot.wim on the USB and its seems that the percsas2 driver appears to be missing. I'm guessing that this is the problem.