Because the data is mirrored on both disks in the array, either one of the disks can fail, as log as one remains functional, without causing the array to fail. This is because when the RAID controller needs to write data it has to do so on both disks, however, when it needs to read data it can simultaneously fetch two different reads from either disk since the data set on both disks is mirrored. Because of this, the I/O performance characteristics will have slightly lower write performance compared to a single disk, while read performance will be nearly double that of a single disk. Each time a data block is written to the storage subsystem, your RAID controller will write that same data block on both disks, providing fault tolerance should one of the disks fail. Summary: RAID 1 mirrors data at the block level on two disks.I/O Performance: Greatly improved read and write performance.Capacity: VD = (C * n) | VirtualDisk = ( Capacity of one disk * number of disks ).We do not recommend using a RAID 0 for production systems. As such, the risk of data loss due to a drive fault will also scale with the number of disks within the array. Because RAID 0 spreads storage blocks across all of the disks in the array, any disk failure will result in the entire array being lost. A RAID 0 can contain two or more disks, with the maximum number being limited based on the number of disks supported by your RAID controller and available drive bays for your server. As such, the performance will tend to scale with the number of disks within the array. This is due to the ability of the array to simultaneously read or write a block to each of the disks in the array. Because the data is striped across multiple disks, you will see improved read and write performance, especially for larger files. Summary: RAID 0 stripes data at the block level across each of the disks in the array.

Veeam bandwidth calculator