Commentary

Howard Marks
 

Is Deduplication An Excuse To Be Lazy?

I was chatting with a three-letter storage vendor today about its upcoming entry into the data deduplication market. As its reps rattled off the usual benefits of data deduplication, they said administrators could stop running differential and incremental backups and just make full backups since the virtual tape library would deduplicate the data anyway. I see the logic, but the old-time admin in the back of my head is yelling "That's just wrong." What do you think?

I was chatting with a three-letter storage vendor today about its upcoming entry into the data deduplication market. As its reps rattled off the usual benefits of data deduplication, they said administrators could stop running differential and incremental backups and just make full backups since the virtual tape library would deduplicate the data anyway. I see the logic, but the old-time admin in the back of my head is yelling "That's just wrong." What do you think?The idea of only running one type of backup and letting the backup gods sort it all out later is appealing. That's one of the things I like best about the GoVault software I blogged about a few days ago. Keep it simple for the SOHO market.

I guess if you're backing up to an inline deduplicating target like a Data Domain or Overland VTL and aren't having problems meeting your backup window, just making full backups could make life easier. If I had a post-processing VTL like a Sepaton or Exabyte, it requires a bunch more disk for the temporary storage of data waiting to dedupe.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

What do you think? Leave a comment.


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

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek 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. InformationWeek 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.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links