Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

News

1/31/2011
12:19 PM
George Crump
George Crump
Commentary
50%
50%

Backup Deduplication 2.0 Needs Better RAID

As we wrap up our series on what is needed in the next generation of backup deduplication devices, one of the key needs is going to be a better drive protection capability. Today most deduplication systems leverage RAID to provide that drive protection, however as capacities increase, RAID rebuild times are going to get worse. Vendors need to provide a better solution.

As we wrap up our series on what is needed in the next generation of backup deduplication devices, one of the key needs is going to be a better drive protection capability. Today most deduplication systems leverage RAID to provide that drive protection, however as capacities increase, RAID rebuild times are going to get worse. Vendors need to provide a better solution.The first part of the problem is that disk backup systems are always going to be one of the first storage platforms in a data center to adopt larger drive capacities so they can continue to narrow the price gap between disk and tape. As these capacities increase so does the time it takes for RAID rebuilds to complete if a drive fails. With RAID 5 this means a longer period of time that your backups are exposed to complete failure. With RAID 6 while you can sustain a second failure without data loss overall backup and recovery performance is still impacted. Of course the longer the rebuild time the greater the chance that there could actually be a second drive failure.

You may ask yourself "why does a total data loss matter?". Fair question, this is after all backup data. First most backup administrators, armed with disk backup, now count on not having to perform as many full backups, instead running higher numbers of incremental, differentials or synthetic full daily backups. The full backup window may now be designed to happen once a quarter. The time saved by eliminating the weekly full backup has probably been absorbed by some other process. Total data loss is especially costly on backup deduplication systems since its efficiency depends on previous generations of files. A total failure means that the entire deduplication process would essentially need to start all over again.

Until drive manufacturers make drives that never fail, the key is for backup deduplication systems to get through this rebuild process sooner or to use a different process all together. RAID is RAID and the larger drives get the more work will be involved in the rebuild process. There are ways around this though. First you can throw more storage horsepower at the problem. While your are limited to drive mechanics the faster the parity calculations can be done the better. Another option is to not fail the entire drive but to use intelligence to mark out the bad section of the drive and keep on going.

Another option is to use a different data protection algorithm than RAID. There are erasure coding or Reed-Solomon techniques that may have better rebuild times. These and other techniques understand what blocks on a drive contain data and only does the rebuild for those blocks, again faster. The other option, probably least attractive in the disk backup space is mirroring since, again, it is trying to compete with tape.

A final option may be to actually use smaller, faster drives and then through backup virtualization, leverage tape to keep the size of the front end disk smaller. As we discussed in our recent article "Breaking The Top Four Myths Of Tape vs. Disk Backup" tape is not susceptible to the cost per GB scrutiny that disk is when it is used as part of the backup process. It may sound a little like turning back the clock. This small disk based cached backed by an increasingly reliable tape library or even as a front end to a deduplicated disk backend may be an ideal solution.

Additional Blogs in this Series:

Deduplication 2.0 - Recovery Performance Backup Deduplication 2.0 - Density Backup Deduplication 2.0 - Power Savings Backup Deduplication 2.0 - Integration

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
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3493
PUBLISHED: 2021-04-17
The overlayfs implementation in the linux kernel did not properly validate with respect to user namespaces the setting of file capabilities on files in an underlying file system. Due to the combination of unprivileged user namespaces along with a patch carried in the Ubuntu kernel to allow unprivile...
CVE-2021-3492
PUBLISHED: 2021-04-17
Shiftfs, an out-of-tree stacking file system included in Ubuntu Linux kernels, did not properly handle faults occurring during copy_from_user() correctly. These could lead to either a double-free situation or memory not being freed at all. An attacker could use this to cause a denial of service (ker...
CVE-2020-2509
PUBLISHED: 2021-04-17
A command injection vulnerability has been reported to affect QTS and QuTS hero. If exploited, this vulnerability allows attackers to execute arbitrary commands in a compromised application. We have already fixed this vulnerability in the following versions: QTS 4.5.2.1566 Build 20210202 and later Q...
CVE-2020-36195
PUBLISHED: 2021-04-17
An SQL injection vulnerability has been reported to affect QNAP NAS running Multimedia Console or the Media Streaming add-on. If exploited, the vulnerability allows remote attackers to obtain application information. QNAP has already fixed this vulnerability in the following versions of Multimedia C...
CVE-2021-29445
PUBLISHED: 2021-04-16
jose-node-esm-runtime is an npm package which provides a number of cryptographic functions. In versions prior to 3.11.4 the AES_CBC_HMAC_SHA2 Algorithm (A128CBC-HS256, A192CBC-HS384, A256CBC-HS512) decryption would always execute both HMAC tag verification and CBC decryption, if either failed `JWEDe...