News
6/15/2011
01:08 PM
George Crump
George Crump
Commentary
50%
50%

Time To Replace Your Backup Application?

More than half of large organizations say they'll consider a new backup system during the next three years. Here's how to get the timing right.

While the actual percentages vary, there are several surveys stating that over 50% of large organizations are going to at least consider a new backup application over the next three years or so. How do you know if it's time to replace your backup application and--if it is time--what you should be looking for?

One of my problems with these surveys is that the question about backup application replacement is usually phrased something like "Will you consider changing your backup application in the next three years?" Well of course you will consider it, most IT professionals are always open to at least considering a new, better way of doing anything.

Most IT professionals also know that actually switching a backup application is a lot harder than it sounds. You have the obvious challenges of buying the new software, implementing it, and learning how to use it. Despite what vendors say, no application is perfect, so that means you have to also learn what doesn't work like you need it to and develop workarounds for that. Finally you also have to develop a strategy for accessing the legacy data that was created by your old backup application. In short, the new product has to be very compelling or your current application has to have really let you down for you to move beyond consideration to actual switching.

The other variable to consider is whether you can add something to your current backup application that makes it easier to live with, or even more reliable, so that you don't have to throw the whole thing out. Disk backup appliances that do data deduplication are an excellent example of something that can be easily implemented to extend the usefulness of your current application.

At some point, though, change is probably inevitable. What usually drives the change to a new backup application is the rise of a specific platform or operating system. We saw this in the data center as we moved from mainframe to Unix systems, from Unix systems to Windows, and we are seeing it again in the move from Windows standalone servers to virtualized Windows and Linux servers. In each one of these platform shifts, the leading backup application typically changed, as well.

Virtualization of servers may be the most significant of these shifts and, as a result, we are seeing traditional enterprise backup application add or improve virtualized server support, as well as seeing a whole new breed of backup applications. As we discuss in "VMware Backup--Feature or Platform," the IT manager has to decide how they are going to protect the virtualized environment. Is it "just another OS" or is it a platform that is the core of the data protection strategy?

In our next entry we will begin to cover what you should be looking for in a new backup application, starting with: should deduplication be built in or should it be added on?

Track Storage Switzerland on Twitter

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-2015-0986
Published: 2015-05-26
Multiple stack-based buffer overflows in Moxa VPort ActiveX SDK Plus before 2.8 allow remote attackers to insert assembly-code lines via vectors involving a regkey (1) set or (2) get command.

CVE-2015-3808
Published: 2015-05-26
The dissect_lbmr_pser function in epan/dissectors/packet-lbmr.c in the LBMR dissector in Wireshark 1.12.x before 1.12.5 does not reject a zero length, which allows remote attackers to cause a denial of service (infinite loop) via a crafted packet.

CVE-2015-3809
Published: 2015-05-26
The dissect_lbmr_pser function in epan/dissectors/packet-lbmr.c in the LBMR dissector in Wireshark 1.12.x before 1.12.5 does not properly track the current offset, which allows remote attackers to cause a denial of service (infinite loop) via a crafted packet.

CVE-2015-3810
Published: 2015-05-26
epan/dissectors/packet-websocket.c in the WebSocket dissector in Wireshark 1.12.x before 1.12.5 uses a recursive algorithm, which allows remote attackers to cause a denial of service (CPU consumption) via a crafted packet.

CVE-2015-3811
Published: 2015-05-26
epan/dissectors/packet-wcp.c in the WCP dissector in Wireshark 1.10.x before 1.10.14 and 1.12.x before 1.12.5 improperly refers to previously processed bytes, which allows remote attackers to cause a denial of service (application crash) via a crafted packet, a different vulnerability than CVE-2015-...

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.