News
8/13/2008
03:29 PM
George Crump
George Crump
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Tier Matching

Tiered storage can be difficult to manage and one of the challenges to its acceptance is the amount of effort it takes to move data between those tiers. We've written about several methods to move data between tiers in previous blogs, but in some cases the decision isn't that complicated.

Tiered storage can be difficult to manage and one of the challenges to its acceptance is the amount of effort it takes to move data between those tiers. We've written about several methods to move data between tiers in previous blogs, but in some cases the decision isn't that complicated.A great example is Tier 0. As I suggested in our last entry, Tier 0 or Solid State Disk (SSD) really have two options; DRAM-based SSDs or Flash-based SSDs. DRAM-based SSDs are primarily supplied by Solid Data, Texas Memory Systems, and Solid Access. Texas Memory is also shipping Flash-based systems along with traditional storage manufacturers EMC and Sun. Eventually, most storage manufacturers will be supplying some form of Flash-based SSDs.

When deciding what data to place on Tier 0, the decision is straightforward. For all practical purposes, you're looking for applications that are disk I/O bound. Typically, these will be applications whose data you are either short stroking or are considering short stroking. While there are exceptions, for many enterprises these are going to be databases and they will be specific files within those databases. I have previously discussed the decision between DRAM and Flash, but what it comes down to is whether the cost differential of DRAM is justifiable by its significant advantage in write I/O performance. Don't rule DRAM-based SSD out until you look at the price; traditional storage manufacturers may charge a premium for their SSDs (which are Flash only). As a result you may be able to get a DRAM-based SSD from one of the SSD-focused suppliers for not much more money than a Flash-based SSD from one of the storage suppliers adding it to their offering. Tier 1 is for all other production data that needs some level of performance -- the rest of the database application that didn't get to the SSD, for example. We are still a few years away from SSDs being at the point where the entire database application can reside on it. When looking at these solutions, remember that some suppliers like 3PAR and Compellent have solved many of the downsides of short stroking, so if you have an application that needs more performance but you can't quite justify the leap to Tier 0, consideration should be given there. In addition to databases, it makes sense for some file data to be on this tier as well. Tier 2 should be for production systems where performance has to be acceptable but not top end. User home directories that are front-ended by a NAS head are good examples. In my opinion, this type of storage, for now, anyway, needs to still be Fibre Channel in the medium-sized to large data center. Most Tier 2 storage is now as reliable and can take advantage of the same storage technologies (snapshots, replication, etc...) as Tier 1 storage. Also, in many cases they can be in the same storage system. For example, your Tier 1 storage may be just a few shelves of 15k RPM small-capacity drives and your Tier 2 might be several racks of 10k medium-capacity drives. An important point here is not buying the highest-capacity drives available. The higher the capacity drive, the longer a RAID rebuild time. RAID rebuild may be THE issue in production storage. The time it takes to rebuild a RAID 5 or RAID 6 volume continues to increase. It also is another reason I advise against SATA in these two tiers. There are a few vendors that are trying to address RAID rebuild issues and we will do a deeper dive in an upcoming entry. Tier 3 has become very interesting, with many different levels within the tier, and will take a blog entry all by itself. How about next time?

Track us on Twitter: http://twitter.com/storageswiss.

Subscribe to our RSS feed.

George Crump is founder of Storage Switzerland, an analyst firm focused on the virtualization and storage marketplaces. It provides strategic consulting and analysis to storage users, suppliers, and integrators. An industry veteran of more than 25 years, Crump has held engineering and sales positions at various IT industry manufacturers and integrators. Prior to Storage Switzerland, he was CTO at one of the nation's largest integrators.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Threat Intel Today
Threat Intel Today
The 397 respondents to our new survey buy into using intel to stay ahead of attackers: 85% say threat intelligence plays some role in their IT security strategies, and many of them subscribe to two or more third-party feeds; 10% leverage five or more.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-2595
Published: 2014-08-31
The device-initialization functionality in the MSM camera driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, enables MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap interface, which all...

CVE-2013-2597
Published: 2014-08-31
Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that lever...

CVE-2013-2598
Published: 2014-08-31
app/aboot/aboot.c in the Little Kernel (LK) bootloader, as distributed with Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to overwrite signature-verification code via crafted boot-image load-destination header values that specify memory ...

CVE-2013-2599
Published: 2014-08-31
A certain Qualcomm Innovation Center (QuIC) patch to the NativeDaemonConnector class in services/java/com/android/server/NativeDaemonConnector.java in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.3.x enables debug logging, which allows attackers to obtain sensitive disk-encryption pas...

CVE-2013-6124
Published: 2014-08-31
The Qualcomm Innovation Center (QuIC) init scripts in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.4.x allow local users to modify file metadata via a symlink attack on a file accessed by a (1) chown or (2) chmod command, as demonstrated by changing the permissions of an arbitrary fil...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.