Introduction to Enterprise Storage

Date December 14, 2009

This weekend, there was a question posted to serverfault that asked about popular mass storage option. You can find the actual question here, but the gist was that the person asking had large storage requirements (>10TB) and didn’t have much knowledge about enterprise storage options.

I’ve put some thought into writing an “Intro to Enterprise Storage” type post for a while, because I remember back when I got my first SAN, I was confused as to how it was all supposed to hang together. I had used Direct Attached Storage (DAS), but I didn’t know it by that name, and I had used Network Addressable Storage (NAS), though I didn’t know it by that name either. I slowly kludged together a working knowledge of how storage “works”, although I’m certainly still no expert.

Hopefully, I do have enough knowledge to help some other people who may just be starting out. To help the person asking the question, I wrote the following answer. It took enough time that I thought I could make it do double duty as a blog entry, too.

If I got something wrong or left something out, drop me a line in the comments.



There are three types of enterprise storage:

  • DAS – Directly Attached Storage
  • This is storage that is either internal to the machine or is an external array of disks connected to the bus of the computer. Examples would include anything from an internal hard drive to an external USB drive to a 12 bay SCSI RAID array. The defining factor is that the storage is on the local bus.

  • NAS – Network Addressable Storage
  • This is storage that is available over the (usually) TCP/IP network, using higher level protocols. If your desktop has an NFS mount, you can consider that data to be on a NAS server. NAS is a relative idea. The actual storage could be internal hard drives on another server or be a network appliance that does nothing but provide storage. Either way, from the perspective of the client, it’s network addressable. The protocols that are typically included as NAS are NFS, CIFS/Samba, and FTP, though there are probably others

  • SAN – Storage Area Network
  • Network addressable storage used a TCP/IP network to transport data using higher level protocols. Storage Area Networks use lower level protocols to present block devices, and typically they their own network fabric to do it, though not necessarily. There are two very common SAN fabrics: iSCSI and Fibre channel. The traffic is sent to the fabric via a Host Bus Adapter (HBA), which you can think of as a SAN network card.

    iSCSI utilizes its own IP network, and is capable of using standard network adapters and switches, which makes it relatively cheap. iSCSI HBAs are a lot like normal network cards, although many of them perform TCP offloading to conserve processor use on the server. Access control is provided through permitting or denying IP addresses from accessing disk resources. As with any other IP based network, ACLs, firewalls, and routing can be used as traffic control devices, although this is frowned upon by many due to the latency that it causes. Speeds range from 1Gb/s to 10Gb/s for brand new, highly expensive network gear.

    Fibre Channel utilizes a completely separate mesh from existing IP based networks. It requires FC HBAs which are either native fiber transceivers or copper SFP connections. FC switches are available to provide additional network segments. Machines are addressed using World Wide IDs or Names (WWIDs), and access control is provided using these addresses by switches and the SAN storage itself. I’m not sure of the current maximum FC speed, but I know that 4Gb/s is available, and I suspect 8Gb/s is too, for enough money. If not, it will be soon.

    The typical SAN storage is a large array of disks in an expensive, highly redundant enclosure. Using embedded software on the array, the SAN administrator uses the available disks to create slices, identified as Logical Unit Numbers (LUNs), which are presented to the specified servers as raw SCSI devices.

    On the server itself, these devices are treated identically to any local storage. Partitions are created, filesystems are put in place, and data is written normally.

    iSCSI and FC aren’t the only SAN fabrics, but they are the most common. Also available is the ultra fast (40-50Gb/s) ultra expensive (> $500 for an HBA) infiniband fabric, as well as the ultra cheap (off the shelf NICs) relatively slow ATA-over-Ethernet, which is sort of a layer-2 equivalent of iSCSI.

5 Responses to “Introduction to Enterprise Storage”

  1. chewyfruitloop said:

    depending on the device iSCSI can effectively be an external SCSI box with a really long cable that hooks into the ethernet port instead of a SCSI card.
    Unfortunately the more connections your device lets you make, the more expensive it gets.

  2. Scott said:

    Dell also makes a device that’s a sort of hybrid betwen DAS and SAN: the MD3000

    15 drives (up to 2TB each at 7.5KRPM or 600GB each at 15KRPM) and 4 SAS connections back to the hosts. You can split that as 2 SAS connections per server on two connected servers for redundancy or forego the redundancy and connect 4 servers to the device.

    It’s managed like a SAN, but without the expense of a FC switch. RAID levels, Snapshots, The SAS connections still require a HBA, but they are only $200 each and get SAS’s 3Gbps throughput.

    It’s a nice middle ground. We went with one when an old Clariion started to give way.

  3. Jeff Hengesbach said:

    Nice article Matt. I can remember when I first started into NAS versus SAN and scratching my head thinking: couldn’t a better / less similar set of acronyms have been used.

    Since I know you have the time ;) and we all now know ‘what’ these options are; how about ‘why’ use one versus the other?

    Jeff

  4. Daniel said:

    Hi Matt. Good summary article.

    Another poster touched on SAS interconnects, and these are becoming more common – Promise (VTE610sD) HP (MSA2000sa) and IBM (DS3200) all have SAS options on their entry level SANs, and there are SAS switches available now. IBM has a SAS SAN option for it’s Bladecenter S. While they all use 3Gb SAS, I believe they use 4x 3Gb multilane connections per port, so you’re actually talking about a 12Gb interconnect. This may not be the case in the MSA and IBM systems, but it is definitely the case in the Promise unit.

    While I haven’t done the full maths on an infiniband setup, initial numbers suggest it’s not that expensive. The HBAs aren’t really any more expensive than FC HBAs, and the switches seem a lot cheaper. eg I’ve seen a 36 port Mellanox QDR (40Gbps, non-blocking, 2.88Tb/s forwarding) switch for $7k US. Even if there are higher overheads with doing iSCSI over RDMA over IB, you still have a lot more bandwidth available. The SAN head options aren’t so obvious, I admit, so there’s more R&D time involved, but the hardware is cheaper and faster.

  5. popular mass storage options Drija said:

    [...] I did end up using this as a blog entry: http://www.standalone-sysadmin.com/blog/2009/12/introduction-to-enterprise-storage/ December 13, 2009 2:22 am andol +1 For a good write up and for pointing out the difference [...]

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Easy AdSense by Unreal