11:18 AM
George Crump
George Crump

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:

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
Oldest First  |  Newest First  |  Threaded View
Register for Dark Reading Newsletters
Dark Reading Live EVENTS
INsecurity - For the Defenders of Enterprise Security
A Dark Reading Conference
While red team conferences focus primarily on new vulnerabilities and security researchers, INsecurity puts security execution, protection, and operations center stage. The primary speakers will be CISOs and leaders in security defense; the blue team will be the focus.
White Papers
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: No, no, no! Have a Unix CRON do the pop-up reminders!
Current Issue
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
The Impact of a Security Breach 2017
The Impact of a Security Breach 2017
Despite the escalation of cybersecurity staffing and technology, enterprises continue to suffer data breaches and compromises at an alarming rate. How do these breaches occur? How are enterprises responding, and what is the impact of these compromises on the business? This report offers new data on the frequency of data breaches, the losses they cause, and the steps that organizations are taking to prevent them in the future.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.