News
5/28/2010
10:54 AM
George Crump
George Crump
Commentary
50%
50%

The Roll Down Hill Effect Of Primary Storage Deduplication

The adoption rate of deduplication in primary storage has been relatively low so far in primary storage. There are concerns on user's minds about performance impact, data integrity and how much capacity savings they will see. Clearly each of these concerns need to be addressed. When it comes to capacity savings though, there is a key component of capacity savings that might get overlooked, the roll down hill effect of proper primary storage deduplication.

The adoption rate of deduplication in primary storage has been relatively low so far in primary storage. There are concerns on user's minds about performance impact, data integrity and how much capacity savings they will see. Clearly each of these concerns need to be addressed. When it comes to capacity savings though, there is a key component of capacity savings that might get overlooked, the roll down hill effect of proper primary storage deduplication.Thus far the big winner in deduplication has been the backup process. If you are doing weekly full backups then there is plenty of opportunity for redundant data and you can post some incredible efficiency gains. This is not the case, or at least should not be, in primary storage. With the exception of virtualization images its unlikely that you will be able to make double digit storage efficiency gains thanks to deduplication alone. If you see typical efficiency claims of 12X in backup deduplication, expect maybe 5X gain in primary storage deduplication.

If you stop there though your missing an important part of the picture, the roll down hill effect of primary storage deduplication. If, and that is an important if, your primary storage deduplication technology can keep the data in an optimized state throughout its entire life cycle then you can see tremendous residual value in primary storage deduplication. With primary storage deduplication snapshots, replication, clones, extra copies of data (just in case copies) all now come at near zero capacity cost. For example you can perform dumps of your database every ten minutes if you want to, deduplication will curtail the capacity growth that would normally create.

The key issue is if and when primary storage deduplication will need to "re-inflate" to a non-optimized data state. Optimization throughout the data lifecycle and the tiers of storage it is on, is critical for making deduplication make sense in primary storage. In fairness there may be a time you want to re-inflate on purpose and remove dependency on the deduplication hash table. That is going to depend on how much you trust your deduplication technology to maintain its meta-data and provide rich data integrity features.

Deduplication technology tries to fix the capacity explosion problem faced by most data centers. Where deduplication is being successful right now, in backup repositories, is trying to fix that problem after it has already occurred. Primary storage deduplication that maintains data in its optimized state fixes the problem before it becomes a problem. If properly implemented primary storage deduplication could have significant reduction on the storage demands of your data center.

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
Comments
Threaded  |  Newest First  |  Oldest First
karthickkandaiyah2
50%
50%
karthickkandaiyah2,
User Rank: Apprentice
12/27/2012 | 4:01:16 PM
re: The Roll Down Hill Effect Of Primary Storage Deduplication
good one
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-2012-2808
Published: 2015-04-01
The PRNG implementation in the DNS resolver in Bionic in Android before 4.1.1 incorrectly uses time and PID information during the generation of random numbers for query ID values and UDP source ports, which makes it easier for remote attackers to spoof DNS responses by guessing these numbers, a rel...

CVE-2014-9713
Published: 2015-04-01
The default slapd configuration in the Debian openldap package 2.4.23-3 through 2.4.39-1.1 allows remote authenticated users to modify the user's permissions and other user attributes via unspecified vectors.

CVE-2015-0259
Published: 2015-04-01
OpenStack Compute (Nova) before 2014.1.4, 2014.2.x before 2014.2.3, and kilo before kilo-3 does not validate the origin of websocket requests, which allows remote attackers to hijack the authentication of users for access to consoles via a crafted webpage.

CVE-2015-0800
Published: 2015-04-01
The PRNG implementation in the DNS resolver in Mozilla Firefox (aka Fennec) before 37.0 on Android does not properly generate random numbers for query ID values and UDP source ports, which makes it easier for remote attackers to spoof DNS responses by guessing these numbers, a related issue to CVE-2...

CVE-2015-0801
Published: 2015-04-01
Mozilla Firefox before 37.0, Firefox ESR 31.x before 31.6, and Thunderbird before 31.6 allow remote attackers to bypass the Same Origin Policy and execute arbitrary JavaScript code with chrome privileges via vectors involving anchor navigation, a similar issue to CVE-2015-0818.

Dark Reading Radio
Archived Dark Reading Radio
Good hackers--aka security researchers--are worried about the possible legal and professional ramifications of President Obama's new proposed crackdown on cyber criminals.