News
1/13/2011
03:13 PM
George Crump
George Crump
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Backup Deduplication 2.0 - Integration

Deduplication has moved from a risky hard to explain technology to one that is almost expected by customers from a disk backup device. Next generation backup deduplication systems are going to require a new set of capabilities to make them more than just disk backup. They will have to integrate with the backup software, begin to provide power management, and there needs to be a greater focus on recovery performance.

Deduplication has moved from a risky hard to explain technology to one that is almost expected by customers from a disk backup device. Next generation backup deduplication systems are going to require a new set of capabilities to make them more than just disk backup. They will have to integrate with the backup software, begin to provide power management, and there needs to be a greater focus on recovery performance.Deduplication can now be delivered as either stand alone hardware or as a module to the backup software. In general a hardware appliance should have the advantage of being more globally useful, meaning you can send backup data streams from a variety of backup sources. Not only specific backup software but also dump commands within applications. The challenge is that in most cases the software has no idea what is going on behind the scenes, including when that data is being replicated or how to use that replicated data. Software deduplication, delivered as part of a module within a backup software application, has the advantage of a tighter integration. In other words the backup application knows that data is being deduped and should be able to leverage that fact.

Hardware deduplication vendors though are quickly embracing available API sets to integrate with backup applications. The most notable example today is Symantec's OpenStorage API that we detailed a while back in "A Backup API". With a backup API in place, hardware vendors can integrate with the backup application to improve performance and allow operations like replication to be controlled through the backup GUI instead of it having to be a separate process controlled through the backup appliance GUI.

Simple integration is just the beginning. As we discussed in our recent article "Integrating Disk Backup With Backup Software" we are beginning to see backup hardware suppliers create specific modules that will increase their integration capabilities with software, even if that software does not have a formal API set. We are also seeing some vendors provide backup application specific modules that can increase performance by offloading some of the data that needs to be processed by the deduplication system. In essence dividing the load up between the backup server and the disk backup appliance. We expect to see this trend continue.

Another challenge with backup deduplication hardware is power and space efficiency. A shortcoming of disk when compared to tape is clearly one of power consumption and with some disk systems the amount of data center floor space they consume. While you can throw plenty of darts at tape, one thing that can be denied is its power or density. In our next entry we will cover what needs to be improved when it comes to data center efficiency.

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
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
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-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.