![]() | Technology Reference Guide 2. Hardware E. Disk Subsystems |
| What is it? A disk subsystem can be as simple as a hard disk and its associated controller. Within the context of network hardware, this refers to the mass storage system used by the file server, or possibly an application server. The two critical issues connected with server disk subsystems are speed and reliability. It is critical to minimize the time required to transfer data to and from the disk subsystem, since I/O requests form the bulk of the traffic across the network. There is a direct correlation between the speed of file access, and the users perception of the networks response time. Reliability and data security form the other major design consideration. Since the file server is designed to be the central repository of files on the network, it is critical that the integrity and availability of the files be insured. Disk subsystems are therefore designed to provide redundancy. This means that the subsystem will try to insure that it has at least two copies of the data. This might mean attaching a second disk to a server disk controller, and writing data to both disks at once. That way, if one disk fails, the other will have a good copy of the data. Software or hardware can be used to direct this process. Netware calls this arrangement disk mirroring. If both an additional controller and disk drive are added, the system can be protected against a controller failure as well. Novell calls this disk duplexing. A side benefit of these duplicate disks is that it becomes possible to split a disk access between two disks, retrieving half the data from each one. This speeds up the disk access. What does it do? RAID levels are typically referred to as RAID-1 through RAID-5, though some creative marketing efforts have produced some references to higher levels. The levels refer to the sophistication of the data redundancy. RAID-5 is more complex than RAID-1.
How is it used? Where do I get more information? |