raid卷深度分析（Raid volume depth analysis）.doc

raid卷深度分析（Raid volume depth analysis） Depth parsing RAID type comprehensive perspective RAID 10 advantage 2010-01-04 10:29 | 96 reading | [comment] has 0 comments Source: fuwuqi | Author: | collection to my network When I was a newcomer to technical services, I knew nothing about system management, when one of the cool topics we had always thought was RAID--s inexpensive (independent) disk redundancy array. At that time, RAID was a panacea for our storage problems. Through RAID, we can extend the file system bigger, higher throughput, and can also increase the redundancy so that we can bear the risk of loss of the disk risk at this time happened more often. With the rise of NAS (Network Attached Storage) and SAN (storage local area network) devices, we no longer need the skills that go deep into physical storage and then adjust physical storage to meet system requirements. Thats not a good thing. We just offload the storage to external devices, which does not change the fact that we need to understand the storage in depth, and we still need to adjust storage to meet the specific needs of the system on the basis of understanding. For the past five or ten years, people seem to have mistaken the idea that RAID is somewhat equivalent to system backups. Actually, it is not. RAID is a fault tolerant form. Backup and fault tolerance are different concepts. Backups enable you to recover data after a disaster occurs. Fault tolerance is the probability of disaster reduction. You can think of a fault tolerance as putting a guardrail at the top of the cliff, while backup is setting up a hospital at the bottom of the cliff. Fences and hospitals are all you want, but they are totally different things. Once we begin to implement RAID on the drive, whether it is locally connected or stored on the network remote equipment, now we can be selected according to the business of four main RAID solution: RAID 1 (mirror); RAID 5 (with parity striping); RAID 6 (with double check code bands