Database Recovery from failed Server SAS drives

If you decided to run your database off on a RAID configuration, there are two types of activity to consider – reading and writing performance. When it comes to data writing, the RAID5 Array is relatively slow. It goes through at least four different disk operations to write data. With enough busy database server, it can a little hard to choose which array fits best. The RAID5, however, is the worst choice among them. RAID10 is usually recommended for databases. If you have a small database and if there is no bottleneck risk, another parity scheme – RAID6 is also a good option. RAID6 mitigates failure risks by having a second parity disk, requiring three disk failures to cause data loss. A customer contacted us for help regarding RAID configuration for a database. After evaluating the case and customer’s confirmation that safety was the main concern, our engineers set up RAID 6 Array.