![]() This way even if you had a power cut as data was being written, any data committed to the RAID controllers cache would be preserved by the battery to be written to the drives when power is restored. If you really depend on your data I would recommend a hardware RAID controller with battery backed cache. In your situation the rebuild time shouldn't be too bad, but software RAID controllers aren't great. RAID 6 and 60 are also hampered by these issues but can tolerate another drive dropping during the stressful rebuild so the problem isn't quite so bad. RAID 5 is slower than RAID 1 or 10 for rebuilds due to the parity calculations. The typical method to defeat this is to employ RAID 1/10/6/60. It's better to think of probablity of URE's rising with the overall RAID volume size rather than number of drives which is why this issue is being considered more and more with todays large drive sizes. During rebuilds the drives can be quite stressed and rebuilds may fail if another drive has any URE's (unrecoverable read errors). They fail in different ways that SoftRAID's heuristics don't. SoftRAID's predicative powers on SSD's is as big of a differential. That isn't a 'performance' difference but it is a functionality difference. ![]() software RAID has not been a possibility for shared storage resources in. The general consensus is that RAID5 rebulid times are getting quite high for large RAID 5 volumes. If this is a 4 drive HDD array than SoftRAID's drive health monitoring is more than substantially better than the 'Disk Utility' solution. steadily growing in recent years as a cost-effective alternative to SCSI.
0 Comments
Leave a Reply. |