I am assuming your RAID0 array is established / controlled either by the mobo's chipset or by an add-on card in the PCI slots - that is, it is NOT done by Windows' own software. Once you create a good array with that sort of controller system, it appears to Windows as just another hard drive - well, almost. Backing up and restoring data to it should not be affected by the fact that it is really a RAID0 array, not just one ordinary drive.
The "well, almost" part is because, although it is just another disk to Windows, it is a disk of a type Windows does not already know how to handle in terms of communications. Hence, like some other types of devices (e.g., a SCSI drive), Windows needs a driver installed to handle the RAID0 array. Given that, there are two branches of where this goes next.
Your stated problem is about Restoring from one drive to the array, and so I assume - maybe wrongly! - that you are trying to restore data to a data storage device only, and NOT trying to create a new boot device to be used as your C: drive. If that is the case, then Windows will be booting from a regular HDD it already understands, and during that process it can also load the required drivers so that a second HDD (in reality, a RAID0 array) can be used. That process is straightforward. You first create the RAID0 array using your controller and its built-in software tools. Then you follow the instructions that come with your RAID system to find the drivers necessary on a disk or website and install them in the Windows you're already running. Once you reboot, Windows will have everything it needs to deal with the array and it will show up in My Computer as a new drive, apparently just a single disk.
Now, if I was wrong and you plan to have this new RAID0 array be your C: drive from which you boot the system, it gets more complicated. The dilemma is that Windows does not normally know how to deal with a RAID0 array, so it can't boot from such an array without help. That help has two parts, and one of those will require that you re-install Windows (unless you want to live with a work-around). The first small part is that, as you create your new RAID0 array, you must be sure to tell that RAID system that this will be your boot device so it can install the proper info in its Partition Table / MBR files on the disks. The other part is that you must re-install Windows, this time making use of the screen that asks if you need to permanently install some new drivers that become a part of this particular Windows installation. You hit the right key (F6) and must load the drivers from a removable device like a floppy drive (or maybe a USB "drive" - read your RAID manual). When installed this way, your Windows WILL know how to handle the RAID0 array for boot purposes and all is well.
The "work-around" I mentioned for systems trying to boot from a RAID0 array without the drivers installed amounts to using a Windows feature that asks if you wish to load special device drivers from floppy disk EVERY TIME you boot up. So you can keep the device (floppy diskette?) in the machine and intervene in the boot process every time to install those drivers for this one boot. Not very convenient, but it does avoid a re-install.
As I said, none of this latter re-install process is necessary at all IF you plan to use the the RAID0 array just as a data device, and will always boot from a non-RAID disk.