Can't restore RAID volume backup. File recovery is very slow and crashes !

Using Acronis True Image 2016, I created a backup of a 2x3TB RAID 0 volume on my GA-990FXA-UD3 motherboard. This is a data volume, not the boot drive. There is about 2TB of data. It was backed up to a single 5TB SATA drive connected to a hotswap tray.

Unfortunately, my internal RAID volume crashed, and I wanted to restore the data, to the same physical RAID volume on the same motherboard and same controller.

Here is the problem : True Image 2016 complains that it can't restore the backup in disk mode or partition mode !

It's simply not possible to select the AMD RAID volume as a target. There is no explanation in the software as to why not !

The only option available seems to be to do a "file recovery". I started doing so, and after 1 hour, it had restored less than 10GB, and in addition, True image crashed ! The resource monitor showed an average write speed of between 15 and 25MB/s.

The backup drive is capable of up to 200MB/s read speed. The target file system is also capable of 200MB/s write speed too, both concurrently.

So, it seems the file recovery is working at about 10% of the speed of  the source and restore disk only. And it's completely unreliable.

The only method that I found that worked was to mount the backup to a local drive letter, and use explorer to copy the files from the mounted volume back to the RAID volume. That provides a speed of about 100MB/s , and explorer says it's going to take about 7 hours to restore the full 2.2TB.

So, questions :

1) why does True image not allow me to restore to the same RAID hardware the backup was created from in disk mode or partition mode ?

2) why does True image file recovery run SO SLOW at 15MB - 25MB/s ?

3) why does True image file recovery crash after an hour ?

And

4) why can't True image file recovery work as reliably and as fast as mounting the image, highlighting all the files on the volume, and doing copy & paste ? At least the backup appears to be restorable . Just not through the normal True Image recover UI.