News
1/7/2010
02:52 PM
George Crump
George Crump
Commentary
50%
50%

Do We Need Tier 1 Storage?

Tiered storage often means the development of a storage strategy that moves data from fast, expensive storage to slower SATA based storage. Tiered storage can also refer to the quality of the storage. A tier 1 storage system may have a higher level of reliability and DR functionality than a tier 2 system. The delta between the quality and capabilities of these tiers is quickly eroding, which makes the question a fair one to ask.

Tiered storage often means the development of a storage strategy that moves data from fast, expensive storage to slower SATA based storage. Tiered storage can also refer to the quality of the storage. A tier 1 storage system may have a higher level of reliability and DR functionality than a tier 2 system. The delta between the quality and capabilities of these tiers is quickly eroding, which makes the question a fair one to ask.When using "tier" to refer to the quality and capability of the system the focus often centers on a tier 1 storage platform. This is most often thought of in terms of large monolithic systems traditionally supplied by EMC and HDS. These systems often build out one frame at a time with drives being added to the frame as capacity is needed. The systems often have advanced software and backend storage interconnects to offer extremely high performance and reliability. Their use is often confined to data centers with extreme uptime requirements and performance needs.

Tier 2 systems offered by companies like NetApp, Xiotech, Compellent and Nexsan are typically represented by more modular systems where capacity is added to a storage compute engine one shelf at a time. These shelves typically have the drives pre-installed. These systems often have moderate storage software with moderate storage interconnects. The scaling and performance of these architectures is significantly greater than it used to be. As a result tier 2 systems often meet the storage I/O needs of many data centers. Eventually however there can be a limit when scaling. At some point capacity or I/O demands could outstrip the capabilities of the storage compute engine. This used to mean either the addition of an additional storage system or the upgrade to a tier 1 storage platform.

Blurring the line is systems with more clustered architectures like those from 3PAR, Isilon and Pillar Data. Even EMC has jumped into more of a clustered storage approach with their VMAX architectures. Clustered storage systems address the limitations of modular and eventually even monolithic systems by offering greater scale and performance. Most of these systems can grow performance and capacity independently. The result is that sophisticated scalable architectures are no longer the sole domain of tier 1 storage.

If performance and scale are no longer the sole property of tier 1 storage the remaining differentiation then becomes how does the software differentiate itself. The expectation of tier 1 storage systems is that they will offer non-disruptive upgradability, a resilient architecture that can maintain performance during failure and a multi-site, multi-mode disaster recovery capability.

For example the capability to replicate data synchronously (mirrored) to a second location miles away, then from that second location replicate (asynchronously) to a third location hundreds of miles away. The challenge is first that not every data center needs this kind of reliability and if they do companies like 3PAR, NetApp and others are closing the gap on the software side to bring this type of advanced functionality to the other storage tiers.

When tier one storage vendors start using standard hardware and more common interconnect architectures like clustering, the focus centers on the quality of the storage software. If the software capabilities of what is traditionally considered tier 2 or clustered storage closes the gap between its tier 1 software counterparts, you are left wondering why use tier 1 storage at all or at least including more vendors in the tier 1 designation.

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-2013-6501
Published: 2015-03-30
The default soap.wsdl_cache_dir setting in (1) php.ini-production and (2) php.ini-development in PHP through 5.6.7 specifies the /tmp directory, which makes it easier for local users to conduct WSDL injection attacks by creating a file under /tmp with a predictable filename that is used by the get_s...

CVE-2014-9652
Published: 2015-03-30
The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field during a copy of a truncated version of a Pascal string, which might allow remote atta...

CVE-2014-9653
Published: 2015-03-30
readelf.c in file before 5.22, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not consider that pread calls sometimes read only a subset of the available data, which allows remote attackers to cause a denial of service (uninitialized memory ...

CVE-2014-9705
Published: 2015-03-30
Heap-based buffer overflow in the enchant_broker_request_dict function in ext/enchant/enchant.c in PHP before 5.4.38, 5.5.x before 5.5.22, and 5.6.x before 5.6.6 allows remote attackers to execute arbitrary code via vectors that trigger creation of multiple dictionaries.

CVE-2014-9709
Published: 2015-03-30
The GetCode_ function in gd_gif_in.c in GD 2.1.1 and earlier, as used in PHP before 5.5.21 and 5.6.x before 5.6.5, allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted GIF image that is improperly handled by the gdImageCreateFromGif function.

Dark Reading Radio
Archived Dark Reading Radio
Good hackers--aka security researchers--are worried about the possible legal and professional ramifications of President Obama's new proposed crackdown on cyber criminals.