Join Newsletter
Forgot
password?
Register
Trusted Business Advisors, Expert Technology Analysts

Taneja Blog

Taneja Blog / Data Center Systems

FalconStor Dedupe Redux

We talked with Darrell Riddle of FalconStor on their Dedupe Redux, more familiarly known as VTL 7.5 with deduplication. Lots of VTLs have deduplication; it’s rare these days to do any kind of storage on disk without deduping the data.  The challenge is where does dedupe happen and how fast does it happen? Concurrent, Inline, Post-Processing? They all have advantages and disadvantages. Deduping at source (concurrent with the backup process) means smaller data is moving through the pipes; an advantage on busy LANs and a really important deal over WAN bandwidth. Issue: processing for dedupe at the source can slow down backup, which is already overrunning backup windows. The last thing it needs is another factor to make it take longer. Deduping inline takes processing out of the source so it’s not impacting backup process performance, an efficient move for environments with heavy backup requirements. Issue: Inline can suck up bandwidth and you need good-sized pipes; it also needs to be fast so it does not retard backup speeds. Post-process deduping lets data reach the storage target at top speeds for the fastest possible transport speeds and performance; dedup product may be a third-party software or running at the storage array level. Issue: Back-end disk storage doesn’t have to be huge because data is still getting deduped, but front-end cache and throughput should be very fast so it won’t retard incoming performance while deduping.

Dedupe vendors of course talk about how source, inline or post is the BEST – the “best” depending on what they make, of course. But there isn’t one “best,” there are different environments and architectures that will benefit the most from different dedupe choices, often within the same enterprise.

FalconStor’s VTL 7.5 is stepping up the game for everyone because they have made a way to do all three, and do them well. The FalconStor VTL could already flexibly dedup at the current and post positions, and now they have added inline capabilities to serve all three dedupe choices. FalconStor Turbo also lowers cycles and boosts speeds at the post and current dedupe locations. We would like to see Turbo added to inline; but even now flexible choices with good –to-exceptional speeds allow customers to tailor dedupe processes to differing systems and infrastructure. We hope to put their ingest and recovery speeds through their paces in our company labs soon, and salute FalconStor for this breakthrough flexibility in VTL-based deduplication.

Bookmark and Share
  • Premiered: 05/09/12
  • Author: Taneja Group
Topic(s): dedup Dedupe Deduplication FalconStor VTL 7.5

Comments

There are no comments to display. Scroll down to leave your own!

 

Leave a Comment

You must be logged in to comment. Click here to log in or register if you don't have an account.