News
10/16/2009
12:24 PM
George Crump
George Crump
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Here Comes Automated Storage Tiering

At Storage Networking World, at least one new category in storage is coming to the forefront; Automated Storage Tiering. These are typically devices that can sit in front of your existing storage platform and allow some of it to leverage a high speed solid state front end without you manually having to move data to a Solid State Disk (SSD).

At Storage Networking World, at least one new category in storage is coming to the forefront; Automated Storage Tiering. These are typically devices that can sit in front of your existing storage platform and allow some of it to leverage a high speed solid state front end without you manually having to move data to a Solid State Disk (SSD).The companies in this space include Avere, Dataram, Gear6 and Storspeed. There are other forms of these products from Compellent and NetApp that either can do dynamic data placement or can provide a large SSD as a front end cache. These solutions however are limited to a single storage system and only work on the respective manufacturers products.

Integrating stand alone SSD or even SSD as a drive type in a storage system is achievable as we state in our recent article "Integrating SSD and Maintaining Disaster Recovery", but what if you don't have the time or what if your environment simply is too difficult to apply these procedures?

Automated Storage Tiering attempts to address the challenge of integration and provide increased optimization of tier 0 storage. After all if you are paying 15X the cost for your tier 0 storage, you don't want even 10% to be empty if you can avoid it.

The basic architecture behind automated tiering is to place the system inline between the storage and the servers. It then will act as a large, in some cases, giant, cache or I/O accelerator. Most of the systems today are DRAM based and then are adding flash SSD as a second tier. Typically the solutions will automatically cache reads and writes to the device. There are options for the storage manager to hard set or hard exclude certain data sets from the cache.

One of the differentiations between the automated tiering systems is going to be on protocol. Some will be block I/O focused and others network file system focused. The network file system storage devices may be able to provide greater analytics. There will also be debate around how the device is really used. Is the device a big cache that simply accelerates the current storage or is the device really a storage platform that leverages the legacy storage as the slowest tier in its available storage tiers?

Automated Storage Tiering is now a legitimate category. How we use this category to help IT to meet continuing storage I/O performance demands vs. some of the other options available to us is the next step.

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
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.