Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

George Crump

How To Develop Multi-Vendor Backup Strategy

Try to find one app that gives good generic coverage, then pinpoint certain applications or environments that need extra attention.

In my last column I discussed how consolidating all your backup processes to a single application is almost impossible given today's environment. It has been months since a column has generated that much email traffic. People are strangely passionate about backup. I heard from vendors questioning my sanity, and backup administrators who confirmed that multi-vendor backup is a reality but wanted some options on how to deal with the mixed environment.

An enterprise backup application is one that attempts to protect more than just one application, operating system, or environment such as VMware or Hyper-V. It also tends to support a broad range of backup devices such as tape libraries, disk backup appliances, and cloud providers. There are a dozen or so of these enterprise backup applications to choose from.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Point solutions or backup utilities are products that target a particular virtualized environment, or specific applications such as SQL, Exchange, SharePoint, and Oracle. There are dozens if not hundreds of these products on the market today. This creates a challenge for IT professionals entrusted with protecting an organization’s data assets. Do they use a single enterprise solution or a suite of backup utilities?

[ Read No Disaster Recovery Plan? No Excuse. ]

We just completed a webinar about the challenges facing enterprise backup. We did a live poll of the viewers, asking how many backup applications they had in place. Not one organization had standardized on one backup application. But over 50% had more than three backup applications in use.

Clearly, consolidation isn't happening in backup, at least at the software level. Why? As much as the enterprise backup vendors will disagree, there are some things that the point applications do better. Although a case could be made that you have to give up some of the "cool" capabilities of these point solutions for the greater good of a consolidated enterprise backup strategy, many of these point solutions are particularly good at rapid recovery. They're so good, in fact, that managers of those applications might say that recovering their app rapidly is more important than the greater good. As a result, the enterprise ends up with multiple data protection applications.

So what to do? First, an application that can provide generic coverage of most of your environment is an important foundation of any data protection strategy. If the enterprise application can truly give you all you need, stop there. No need to complicate things. But I believe, and our research shows, that most enterprises will benefit from a few solutions targeted at certain applications or environments.

Once you accept mixed backup as fact, the next step is to manage the reality. Understand what backup application is backing up each set of data. In many cases we have found that one set of data is being protected by four or five different applications or utilities. Even the most critical of data probably does not need that many levels of protection.

Once you identify how many redundant copies of data you need of each data set and that those copies are getting made as scheduled, the next step is to develop an understanding of which data set you are going to restore from in different recovery scenarios. We have seen several cases where an application was down for hours while IT struggled to find the right backup copy to restore from. Knowing which copy is the "right" copy is critical.

In my next column I'll discuss the next step: Identifying an umbrella application that can at a minimum provide cross application monitoring and potentially provide a policy engine. Finally, we will end with potentially the best place to consolidate backups: At the backup storage device.



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.