News
2/25/2010
09:21 AM
George Crump
George Crump
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Can Rip And Replacing Storage Solutions Be Good?

When you hear the term "Rip and Replace" it is not typically considered a good feature. In fact most of the time you hear it will be from a vendor stating that their solution is NOT rip and replace. Which of course they expect you to take to be good. Are there times though were rip and replace could be a good thing?

When you hear the term "Rip and Replace" it is not typically considered a good feature. In fact most of the time you hear it will be from a vendor stating that their solution is NOT rip and replace. Which of course they expect you to take to be good. Are there times though were rip and replace could be a good thing?The advantage that a storage system or software application has that is not rip and replace, is it means you can leverage what you already have in place. Most of the time that is exactly what you would prefer to do. Your current storage system or software, despite its weaknesses, is the devil you know and there is a certain amount of comfort in that. The problem is, however, what if your storage system or software has now become a collection of band-aids, extended to the point of breaking?

I'm a big fan of using what you have but sometimes in storage especially we can try to get too much mileage out of our current systems. Tape library systems and old storage arrays come to mind. In the tape library case you typically try to augment what you have with disk or if you do upgrade the tape device you do so with a similar drive type. What if a newer system that may require a rip and replace will actually save you more money than keeping your current system. Isn't it worth going through the effort?

If your new storage system or tape library can radically improve the way you manage storage or fundamentally reduce the costs, then a clean sweep might very well be in order. In the storage system use case this may be a new system that can leverage thin provisioning and even migrate old data into a thin provisioned volume. Another use case may be a system that can save on space, power and cooling costs. These capabilities and others have value, provide a rapid return on the investment and are difficult to add to existing arrays.

Most of the time you want a combination of these new capabilities to justify a rip and replace move but sometimes even a single capability can justify the move. For example I spoke with a data center manger recently that moved to a new thin provisioning system, and they were able to purchase 40% less storage capacity then what they had previously. Considering they previously had almost 50TBs of storage this represents a significant cost savings as well as power, space and cooling reductions.

Of course extending a system instead of ripping it out also has its appeal, Solid State Disk, space optimization and automated tiering are ideal examples of extending the life of an existing system. They can increase performance or capacity without the need to go to a more expensive high performance disk array or add more trays of drives. An example here is a data center manager I spoke with that added a deduplication system to his environment and reduced his capacity needs by 30%. Considering he had over 75TBs of data this will allow him to postpone his storage purchases for a year.

As always you have to weigh the pros and cons to see what makes the most sense. Can a capability be added to an existing system? Does extending its life a little further make more sense or is it time to send it packing? Our recommendation is to make sure you don't hear rip and replace and rule that potential solution out.

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-7392
Published: 2014-07-22
Gitlist allows remote attackers to execute arbitrary commands via shell metacharacters in a file name to Source/.

CVE-2014-2385
Published: 2014-07-22
Multiple cross-site scripting (XSS) vulnerabilities in the web UI in Sophos Anti-Virus for Linux before 9.6.1 allow local users to inject arbitrary web script or HTML via the (1) newListList:ExcludeFileOnExpression, (2) newListList:ExcludeFilesystems, or (3) newListList:ExcludeMountPaths parameter t...

CVE-2014-3518
Published: 2014-07-22
jmx-remoting.sar in JBoss Remoting, as used in Red Hat JBoss Enterprise Application Platform (JEAP) 5.2.0, Red Hat JBoss BRMS 5.3.1, Red Hat JBoss Portal Platform 5.2.2, and Red Hat JBoss SOA Platform 5.3.1, does not properly implement the JSR 160 specification, which allows remote attackers to exec...

CVE-2014-3530
Published: 2014-07-22
The org.picketlink.common.util.DocumentUtil.getDocumentBuilderFactory method in PicketLink, as used in Red Hat JBoss Enterprise Application Platform (JBEAP) 5.2.0 and 6.2.4, expands entity references, which allows remote attackers to read arbitrary code and possibly have other unspecified impact via...

CVE-2014-4326
Published: 2014-07-22
Elasticsearch Logstash 1.0.14 through 1.4.x before 1.4.2 allows remote attackers to execute arbitrary commands via a crafted event in (1) zabbix.rb or (2) nagios_nsca.rb in outputs/.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Where do information security startups come from? More important, how can I tell a good one from a flash in the pan? Learn how to separate ITSec wheat from chaff in this episode.