News
1/20/2010
11:18 AM
George Crump
George Crump
Commentary
50%
50%

Automated Tiering Methods

A few entries ago we opened up the subject of Automated Tiering with an explanation of why the technology is becoming so needed. As this series of entries continues we will review various storage vendors specific approach to automated tiering, but first it is helpful to understand the common methods that are employed.

A few entries ago we opened up the subject of Automated Tiering with an explanation of why the technology is becoming so needed. As this series of entries continues we will review various storage vendors specific approach to automated tiering, but first it is helpful to understand the common methods that are employed.Automated tiering is the dynamic placement of data on different classes of storage based on parameters that define how that data is being used, most often its level of activity that defines where the data goes. These classes of storage typically range from some form of memory based storage (RAM, FLASH SSD or DRAM SSD) to Fibre/SAS mechanical drives to SATA drives. Depending on the vendor they either supply all of these classes of storage or they merely provide the automated tiering intelligence and you provide the classes of storage.

Most of the focus with automated tiering is moving active data to the fastest tier possible. The idea is maximize the benefits of the most expensive and fastest class of storage. If you are paying more per GB for the memory based tier of storage then you want to make sure you buy as little as you have to and that it is almost always near full. Running memory based storage at 50% utilization is a significant waste of resources.

The first method of automated tiering is to treat this faster tier of storage as a large cache, similar to cache technologies that already exist on drives and storage systems today. The main difference is that they are significantly larger. The concept has merit. Cache technology is certainly well vetted yet vendors can still add value by customizing the approach. It can have a safer feel to it as well by using it in a read only mode, meaning that if the automated tiering device fails you have not lost data. Of course that also means in write heavy environments you would see no performance benefits.

Most of the caching systems and all of the second method of automated tiering solutions have the ability to treat this higher speed tier as something more permanent. Data will reside uniquely on a particular tier for a significant time. That time could be a few seconds, in the case of cache based systems, up to a few days on the second method, which I'll call the storage method for lack of a better term. The storage method systems also typically have a tunable setting that allows you to set how long data is uniquely on each tier of storage. While this method should lead to further performance boosts it may also lead to data loss if the automated tiering device fails or the tier which has the data fails. Typically though the storage method systems provide for some HA (highly available) functionality.

Next up we will look at the different protocols that are supported (file and block) as well as the level of granularity (block, file, LUN) that these solutions tend to offer.

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

Subscribe to our RSS feed.

George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Find Storage Switzerland's disclosure statement here.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
10 Recommendations for Outsourcing Security
10 Recommendations for Outsourcing Security
Enterprises today have a wide range of third-party options to help improve their defenses, including MSSPs, auditing and penetration testing, and DDoS protection. But are there situations in which a service provider might actually increase risk?
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-4692
Published: 2015-07-27
The kvm_apic_has_events function in arch/x86/kvm/lapic.h in the Linux kernel through 4.1.3 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by leveraging /dev/kvm access for an ioctl call.

CVE-2015-1840
Published: 2015-07-26
jquery_ujs.js in jquery-rails before 3.1.3 and 4.x before 4.0.4 and rails.js in jquery-ujs before 1.0.4, as used with Ruby on Rails 3.x and 4.x, allow remote attackers to bypass the Same Origin Policy, and trigger transmission of a CSRF token to a different-domain web server, via a leading space cha...

CVE-2015-1872
Published: 2015-07-26
The ff_mjpeg_decode_sof function in libavcodec/mjpegdec.c in FFmpeg before 2.5.4 does not validate the number of components in a JPEG-LS Start Of Frame segment, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via craft...

CVE-2015-2847
Published: 2015-07-26
Honeywell Tuxedo Touch before 5.2.19.0_VA relies on client-side authentication involving JavaScript, which allows remote attackers to bypass intended access restrictions by removing USERACCT requests from the client-server data stream.

CVE-2015-2848
Published: 2015-07-26
Cross-site request forgery (CSRF) vulnerability in Honeywell Tuxedo Touch before 5.2.19.0_VA allows remote attackers to hijack the authentication of arbitrary users for requests associated with home-automation commands, as demonstrated by a door-unlock command.

Dark Reading Radio
Archived Dark Reading Radio
What’s the future of the venerable firewall? We’ve invited two security industry leaders to make their case: Join us and bring your questions and opinions!