News
5/28/2010
10:54 AM
George Crump
George Crump
Commentary
Connect Directly
RSS
E-Mail
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
Newest First  |  Oldest First  |  Threaded View
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
Flash Poll
Current Issue
Cartoon
Threat Intel Today
Threat Intel Today
The 397 respondents to our new survey buy into using intel to stay ahead of attackers: 85% say threat intelligence plays some role in their IT security strategies, and many of them subscribe to two or more third-party feeds; 10% leverage five or more.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6306
Published: 2014-08-22
Unspecified vulnerability on IBM Power 7 Systems 740 before 740.70 01Ax740_121, 760 before 760.40 Ax760_078, and 770 before 770.30 01Ax770_062 allows local users to gain Service Processor privileges via unknown vectors.

CVE-2014-0232
Published: 2014-08-22
Multiple cross-site scripting (XSS) vulnerabilities in framework/common/webcommon/includes/messages.ftl in Apache OFBiz 11.04.01 before 11.04.05 and 12.04.01 before 12.04.04 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, which are not properly handled in a (1)...

CVE-2014-3525
Published: 2014-08-22
Unspecified vulnerability in Apache Traffic Server 4.2.1.1 and 5.x before 5.0.1 has unknown impact and attack vectors, possibly related to health checks.

CVE-2014-3563
Published: 2014-08-22
Multiple unspecified vulnerabilities in Salt (aka SaltStack) before 2014.1.10 allow local users to have an unspecified impact via vectors related to temporary file creation in (1) seed.py, (2) salt-ssh, or (3) salt-cloud.

CVE-2014-3594
Published: 2014-08-22
Cross-site scripting (XSS) vulnerability in the Host Aggregates interface in OpenStack Dashboard (Horizon) before 2013.2.4, 2014.1 before 2014.1.2, and Juno before Juno-3 allows remote administrators to inject arbitrary web script or HTML via a new host aggregate name.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.