Risk
4/21/2011
02:35 PM
George Crump
George Crump
Commentary
50%
50%

Forget Tape Vs. Disk, Use Them Together

Tape is ideal for third tier backup data and the cost per GB, performance, and reliability make it an ideal compliment to disk backup.

"Tape is Dead" may be a common statement, but it just does not hold true to the reality. Most tape and tape library companies are reporting strong sales growth over the past couple years. User studies indicate that well under 20% of data centers have become disk backup only. In most environments this should no longer be a tape vs. disk conversation, both technologies should continue to be leveraged together.

Most data centers now consider backup disk as the first source of recovery when something has failed. In reality backup disk should be your second point of recovery not your first. As Storage Switzerland discussed in a recent article "Protecting Applications From Storage System Failures" most data centers should not be counting on the backup process at all for mission critical recoveries.

There should be some other form of recovery technology in place that provides direct access to data and a smaller window of time between data protection captures. Disk backup should be the second step in a recovery process when something goes wrong with a high availability (HA) solution or an older point in time of the data set is needed. The disk backup can also be used for primary recovery of less critical systems but we think the number of applications and services that can sustain multi-hour recovery times is decreasing.

Tape should be looked at as the third tier of recovery, when a much older point in time of data is needed or when something goes wrong with the previous two recovery steps. Despite this, there is also a situation where tape should be considered as the primary backup and recovery point. Consider tape first when a very large data set needs to, and can be, transferred across a very high-speed connection.

Tape, if it can be sustained at full streaming performance is incredibly fast, faster than many disk based backup systems. An example of this might be a database environment with a large 200GB+ data set where tape can either be attached directly or via a fibre channel connection. A transfer directly from the database server to tape is often faster than to a backup class disk system. A case can be made that tape is all you need here since many database applications have some other form of availability in place for quick recovery. The purpose of the backup then is to create an archive of the database and to get that data off-site. Something that tape is well suited for.

Tape is ideal for this third tier of backup data thanks to the continued progress of the technology. The cost per GB, performance and now the reliability and shelf life of tape make it an ideal compliment to disk backup. It provides an alternate, offline storage method in case something goes wrong with disk media. In most environments, HA solutions should be the point of first restore, disk backup should be the point of second restore and tape backup should be the safety net. The challenge is that the integration between these three layers is lacking and is something we will discuss in our next entry.

Follow Storage Switzerland on Twitter

George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Storage Switzerland's disclosure statement.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6501
Published: 2015-03-30
The default soap.wsdl_cache_dir setting in (1) php.ini-production and (2) php.ini-development in PHP through 5.6.7 specifies the /tmp directory, which makes it easier for local users to conduct WSDL injection attacks by creating a file under /tmp with a predictable filename that is used by the get_s...

CVE-2014-9652
Published: 2015-03-30
The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field during a copy of a truncated version of a Pascal string, which might allow remote atta...

CVE-2014-9653
Published: 2015-03-30
readelf.c in file before 5.22, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not consider that pread calls sometimes read only a subset of the available data, which allows remote attackers to cause a denial of service (uninitialized memory ...

CVE-2014-9705
Published: 2015-03-30
Heap-based buffer overflow in the enchant_broker_request_dict function in ext/enchant/enchant.c in PHP before 5.4.38, 5.5.x before 5.5.22, and 5.6.x before 5.6.6 allows remote attackers to execute arbitrary code via vectors that trigger creation of multiple dictionaries.

CVE-2014-9709
Published: 2015-03-30
The GetCode_ function in gd_gif_in.c in GD 2.1.1 and earlier, as used in PHP before 5.5.21 and 5.6.x before 5.6.5, allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted GIF image that is improperly handled by the gdImageCreateFromGif function.

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.