News
4/30/2010
12:13 PM
George Crump
George Crump
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Storage Checkers Vs. Chess

Checkers is a two dimensional game where all the pieces have the same ability. Its about covering space. Chess is a complex three dimensional game where all the pieces have different capabilities and there is one common target: the enemy's king. In storage some features begin to look like checkers because they have become so commonplace, but when you dig deeper you find that the capabilities of these features between vendors vary greatly.

Checkers is a two dimensional game where all the pieces have the same ability. Its about covering space. Chess is a complex three dimensional game where all the pieces have different capabilities and there is one common target: the enemy's king. In storage some features begin to look like checkers because they have become so commonplace, but when you dig deeper you find that the capabilities of these features between vendors vary greatly.A great example is snapshot technology. I would be hard pressed to name a storage system vendor or even an operating system that does not have the feature listed. If you have a checkers view of storage, covering the bases, then you will give the feature a check mark and move on. Reality is though that snapshot technology is still different between vendors. Many vendors still have a relatively small limit on the amount of snapshots that can be maintained per LUN or volume because of how the tracking and managing of snapshots will impact performance of the system. Even systems that have seemingly high snapshot limits really should be reviewed with close scrutiny. Thanks to server virtualization you can hit 200+ active snapshots per volume quickly.

Thin provisioning is another technology that seems headed toward the checker status that really should not be. There are still key differences in vendor offerings. The first is how the thin provisioning allocates storage. Many thinly provisioned systems are really just dynamically allocating chunks of capacity as the volumes they are monitoring reach their allocation limits. For example if you define a 1TB volume some systems will allocate volume to its capacity rather than chunks at a time instead of a very fine grained allocation. When this chunk is filled up another chunk is allocated. What this means is that for each volume there is capacity that is allocated and not in use. For some vendors this extra allocation can be quite large, and in a storage system with hundreds if not thousands of volumes it can result in a lot of wasted capacity.

Another key development in thin provisioning, as we outline in our Thin Provisioning White paper, is the ability to migrate from hard volumes to thin volumes as well as reclaim capacity on thin provisioned volumes after data has been deleted from them. These are still relatively new features. Most storage systems do not have it yet and they could be important, especially in larger data centers.

There are other features that are often assumed to be the same yet on further examination are very different between vendors. Capabilities like deduplication, auto-tiering, compression and replication are just a few, even basic capabilities like the actual provisioning of storage can be vastly different on further review. When considering your storage options make sure you are playing chess, not checkers.

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
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-2013-4262
Published: 2014-07-28
svnwcsub.py in Subversion 1.8.0 before 1.8.3, when using the --pidfile option and running in foreground mode, allows local users to gain privileges via a symlink attack on the pid file. NOTE: this issue was SPLIT due to different affected versions (ADT3). The irkerbridge.py issue is covered by CVE-...

CVE-2013-4840
Published: 2014-07-28
Unspecified vulnerability in HP and H3C VPN Firewall Module products SECPATH1000FE before 5.20.R3177 and SECBLADEFW before 5.20.R3177 allows remote attackers to cause a denial of service via unknown vectors.

CVE-2013-7393
Published: 2014-07-28
The daemonize.py module in Subversion 1.8.0 before 1.8.2 allows local users to gain privileges via a symlink attack on the pid file created for (1) svnwcsub.py or (2) irkerbridge.py when the --pidfile option is used. NOTE: this issue was SPLIT from CVE-2013-4262 based on different affected versions...

CVE-2014-2974
Published: 2014-07-28
Cross-site request forgery (CSRF) vulnerability in php/user_account.php in Silver Peak VX through 6.2.4 allows remote attackers to hijack the authentication of administrators for requests that create administrative accounts.

CVE-2014-2975
Published: 2014-07-28
Cross-site scripting (XSS) vulnerability in php/user_account.php in Silver Peak VX before 6.2.4 allows remote attackers to inject arbitrary web script or HTML via the user_id parameter.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Sara Peters hosts a conversation on Botnets and those who fight them.