News
7/14/2008
01:58 PM
George Crump
George Crump
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Block-Level Tiered Storage

Tiered storage no longer has the hype surrounding it that it did a few years ago. The concept was simple -- move data from expensive Fibre drives to inexpensive SATA drives. SATA drive technology was just coming into its own and the price and modest capacity made it a good fit for the concept. As a result, every storage manufacturer on the planet was proposing a tiered storage strategy. There were seminars, Webinars, white papers (guilty as charged, I wrote more than a few of them), yet only a f

Tiered storage no longer has the hype surrounding it that it did a few years ago. The concept was simple -- move data from expensive Fibre drives to inexpensive SATA drives. SATA drive technology was just coming into its own and the price and modest capacity made it a good fit for the concept. As a result, every storage manufacturer on the planet was proposing a tiered storage strategy. There were seminars, Webinars, white papers (guilty as charged, I wrote more than a few of them), yet only a fraction of accounts ever implemented the strategy.Why? Well, it was movement. Movement of data from Point A to Point B in the data center is always a challenge. It is a challenge for backups, it is a challenge for replication, and it is a challenge for ILM or archive strategies. Over the last few weeks I've written about several types of data movement strategies, but none are as simple to implement as block-level tiered storage.

While my term for it isn't as catchy as 3PAR's Nearline for Online or Compellent's data progression, the concept is to have the storage system monitor data at a block level and be able to set policies based on the block itself, typically on the block's age. Basically, if a block of data hasn't been accessed in the last 90 days, move it from expensive Fibre Channel disk to SATA disk. There are two key advantages of this method compared with traditional data movement techniques.

First, block-level tiered storage can operate on almost any type of data. Traditional archiving is focused on file level data, and while there are a few database archive utilities available, they're not in widespread use. Second, the use can be expanded beyond just a simple move from Fibre to ATA. It could be a move from a mirrored Fibre 15k RAID group to a standard RAID 5 group made up with 10k Fibre drives and then eventually to ATA.

Block-level tiered storage works across all platforms connected to the array, with no additional agents to install on those servers, no crawl or file system walks like discussed in previous entries, no worries about upgrades to the OS breaking your data movement application. Essentially, you activate the capability to define your policies and then it just works.

While not a replacement for an archive strategy, this is possibly one of the more practical methods to implement tiered storage. Archiving is going to require understanding the file as a whole, setting retention strategies around that file, possible control modification based on the type of file, and also having the ability to search the content of that file. That said, block-level tiered storage is a cost-effective way to manage the active or near-active data set.

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
Flash Poll
Current Issue
Cartoon
DevOps’ Impact on Application Security
DevOps’ Impact on Application Security
Managing the interdependency between software and infrastructure is a thorny challenge. Often, it’s a “developers are from Mars, systems engineers are from Venus” situation.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0103
Published: 2014-07-29
WebAccess in Zarafa before 7.1.10 and WebApp before 1.6 stores credentials in cleartext, which allows local Apache users to obtain sensitive information by reading the PHP session files.

CVE-2014-0475
Published: 2014-07-29
Multiple directory traversal vulnerabilities in GNU C Library (aka glibc or libc6) before 2.20 allow context-dependent attackers to bypass ForceCommand restrictions and possibly have other unspecified impact via a .. (dot dot) in a (1) LC_*, (2) LANG, or other locale environment variable.

CVE-2014-2226
Published: 2014-07-29
Ubiquiti UniFi Controller before 3.2.1 logs the administrative password hash in syslog messages, which allows man-in-the-middle attackers to obtains sensitive information via unspecified vectors.

CVE-2014-3541
Published: 2014-07-29
The Repositories component in Moodle through 2.3.11, 2.4.x before 2.4.11, 2.5.x before 2.5.7, 2.6.x before 2.6.4, and 2.7.x before 2.7.1 allows remote attackers to conduct PHP object injection attacks and execute arbitrary code via serialized data associated with an add-on.

CVE-2014-3542
Published: 2014-07-29
mod/lti/service.php in Moodle through 2.3.11, 2.4.x before 2.4.11, 2.5.x before 2.5.7, 2.6.x before 2.6.4, and 2.7.x before 2.7.1 allows remote attackers to read arbitrary files via an XML external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) is...

Best of the Web
Dark Reading Radio