{"id":328,"date":"2012-08-03T18:43:08","date_gmt":"2012-08-03T23:43:08","guid":{"rendered":"http:\/\/www.smbitjournal.com\/?p=328"},"modified":"2012-08-04T12:19:01","modified_gmt":"2012-08-04T17:19:01","slug":"choosing-a-storage-type","status":"publish","type":"post","link":"https:\/\/smbitjournal.com\/2012\/08\/choosing-a-storage-type\/","title":{"rendered":"Choosing a Storage Type"},"content":{"rendered":"

While technicalities defining which type of storage is which can become problematic, the underlying concepts are pretty well understood.\u00a0 There are four key types of storage that we use in everyday server computing: local disks, DAS, NAS and SAN.\u00a0 Choosing which we want to use, in most cases, can be broken down into a relatively easy formula.<\/p>\n

The quick rule of thumb for storage should be: Local before DAS, DAS before NAS, NAS before SAN.\u00a0 Or as I like to write it:<\/p>\n

Local Disks -> DAS -> NAS -> SAN<\/em><\/p>\n

To use this rule you simply start with your storage requirements in hand and begin on the left hand side.\u00a0 If local disks meet your requirements, then almost certainly they are your best choice.\u00a0 If they don’t meet your requirements move to the right and check if DAS will meet your requirements.\u00a0 If so, great, if not continue the process.<\/p>\n

That’s the rule of thumb, so if that is all you need, there you go.\u00a0 But we will dive into the “why” of the rule below. The quick overview is that on the left we get speed and reliability at the lowest cost.\u00a0 As we move to the right complexity increases as does price typically.\u00a0 The last two, while very different, are actually the most alike in many ways due to their networked nature.<\/p>\n

Local Disks:<\/strong>\u00a0 Local drives inside your server chassis are your best bet for most tasks.\u00a0 Being inside the chassis means the least amount of money spent on extra containers to hold and power the drives, least physical risk, most solid connection technologies, shortest distance and least amount of potential bottlenecks. Being raw disks, local disks are block devices.<\/p>\n

Direct Attached Storage:\u00a0 <\/strong>DAS is, more or less, local drives housed outside of the server chassis.\u00a0 The server itself will see them exactly like any other local drives making them very easy to use.\u00a0 DAS is simple but still has extra external containers and extra cables.\u00a0 This adds cost and some complexity.\u00a0 DAS makes it easier to attach multiple servers to the same set of drives as this is almost impossible, and always cumbersome, with local disks.\u00a0 So DAS is effectively our first type of physically sharable storage.\u00a0 Being identical to local disks, DAS is a form of block device.<\/p>\n

Network Attached Storage: <\/strong>NAS is unique in that it is the only non-block device from which we have to choose.\u00a0 A NAS, or a traditional file server – they are truly one and the same, is the first of our technologies designed to run over a network.\u00a0 This adds a lot of complication.\u00a0 NAS shares storage out at the filesystem level.\u00a0 A NAS is an intelligent device that allows users over the network to easily and safely share storage because the NAS has the necessary logic on board to handle multiple users at one time.\u00a0 NAS is very easy for anyone to use and is even commonly used by people at home.<\/p>\n

Storage Area Network: <\/strong>SAN is an adaptation of DAS with the addition of a network infrastructure allowing the SAN to behave as a remote hard drive (block device) that an operating system sees as no different from any other hard drive attached to it.\u00a0 SANs require advanced networking knowledge, are surrounded by a large amount of myth and rumor, are poorly understood by the average IT professional, are generally complex to use and understand and because they lack the logic of a NAS they effectively expose a hard drive directly to the network making it trivially easy to corrupt and destroy data.\u00a0 It is, in fact, so easy to lose data on a SAN due to misconfiguration that the most commonly expected use of a SAN is a use case for which a SAN cannot be used.<\/p>\n

Of course there is much grey area.\u00a0 What is normally considered a DAS can be turned into a SAN.\u00a0 A SAN can be direct connected.\u00a0 NAS can be direct connected.\u00a0 Local storage can act as either NAS or SAN depending on configuration such as with a VSA (Virtual Storage Appliance.) \u00a0Many devices are simultaneously NAS and SAN and the determination is by configuration, not by the physical device itself.\u00a0 But in generally accepted use, the terms are mostly straightforward.<\/p>\n

The point being that as we move from left to right in our list we move from simple and easy to difficult and complex.\u00a0 SAN itself is a rock solid technology; it is the introduction of humans and their tendency to do dangerous things easily with SAN that makes it a dangerous storage technique for the average user.\u00a0 As with everything in IT, keeping our technologies and processes simple brings stability and security and, often, cost savings as well.<\/p>\n

There are many times when movement to “the right” is necessary.\u00a0 Local disks do not scale well and can become too expensive to maintain for certain types of larger deployments.\u00a0 DAS, likewise, doesn’t scale well in many cases.\u00a0 NAS scales well but being a non-block protocol is a bit unique and doesn’t always work for our purposes, a good example being HyperV that requires a block device for storage.\u00a0 SAN is the final catchall of storage.\u00a0 If nothing else works, SAN is always there to fall back on – or, as I like to say, SAN is the storage of last resort<\/em>.<\/p>\n

This is a very high level look at the basics of choosing a storage approach.\u00a0 This is a common IT task that must be done with great regularity.\u00a0 I did not intend this post, in any way, to explain any deep knowledge of storage but simply to provide a handy guide to understanding where to start looking at storage options.\u00a0 Exceptions and special cases abound, but it is extremely common to simply skip the best option and go straight to considering something big, expensive and complex and rapidly forget that something much more simple might do the same job in a far superior manner. \u00a0The underlying concept is\u00a0the simplest solution that meets the need is usually the best.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

While technicalities defining which type of storage is which can become problematic, the underlying concepts are pretty well understood.\u00a0 There are four key types of storage that we use in everyday server computing: local disks, DAS, NAS and SAN.\u00a0 Choosing which we want to use, in most cases, can be broken down into a relatively … Continue reading Choosing a Storage Type<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[41],"tags":[60,58,48,32,33],"_links":{"self":[{"href":"https:\/\/smbitjournal.com\/wp-json\/wp\/v2\/posts\/328"}],"collection":[{"href":"https:\/\/smbitjournal.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smbitjournal.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smbitjournal.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/smbitjournal.com\/wp-json\/wp\/v2\/comments?post=328"}],"version-history":[{"count":3,"href":"https:\/\/smbitjournal.com\/wp-json\/wp\/v2\/posts\/328\/revisions"}],"predecessor-version":[{"id":330,"href":"https:\/\/smbitjournal.com\/wp-json\/wp\/v2\/posts\/328\/revisions\/330"}],"wp:attachment":[{"href":"https:\/\/smbitjournal.com\/wp-json\/wp\/v2\/media?parent=328"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smbitjournal.com\/wp-json\/wp\/v2\/categories?post=328"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smbitjournal.com\/wp-json\/wp\/v2\/tags?post=328"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}