Commentary

George Crump
 

Better Storage Practices To Improve Backup

Backup is the thorn in the side of many otherwise smoothly running IT operations. There is probably little coincidence that the newest hire is almost always assigned the backup process or the ramification for missing the assignments meeting. The truth is that backup should be simple -- all you're doing is copying data to tape. The problem in general has nothing to do with the backup process, it has more to do with how primary storage is managed and optimized.

Backup is the thorn in the side of many otherwise smoothly running IT operations. There is probably little coincidence that the newest hire is almost always assigned the backup process or the ramification for missing the assignments meeting. The truth is that backup should be simple -- all you're doing is copying data to tape. The problem in general has nothing to do with the backup process, it has more to do with how primary storage is managed and optimized.The primary problem is size; there is too much data, too much that is stagnant and unchanging. All of this unchanged data has to traverse most often the standard IP network or, best case, a SAN. While disk backup targets, especially those with data deduplication, help to optimally store this backup data, it really doesn't fix the problem at its source.

Fixing problems at the source is where you can derive the most improvement for the least investment. For example, look at real-time compression products like those from Storwize. These solutions compress file-based data in place and, in most cases, achieve better than 60% reduction of data. For user access, data is compressed and decompressed on the fly transparently, with little, if any, performance impacts. The backup application can access the compressed data in its compressed format, effectively cutting in half the amount of data to transport across the network and subsequently stored on backup disk and/or backup tape. Interesting that these inline compression appliances are compatible with deduplication appliances and actually improve their effective reduction rates.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The next step is to look into software that will reduce the amount of data sent across the network in the first place. The source-side reduction backup applications can either perform deduplication like EMC's Avamar or block-level incremental backups like SyncSort's Backup Express. While deduplication has the advantage of maximum backup disk storage optimization, block-level incremental technology (BLI) creates a backup volume that can be utilized for other purposes because it itself is a readable file system. Also, BLI has less impact on the server being protected, making more frequent backups more practical.

Finally, it makes sense to archive all this stagnant data off primary storage. Most studies indicate that more than 80% of this data can be archived and moved out of the backup process in its entirety. Using disk archive products like those from Permabit, NexSAN, or Copan Systems can be more aggressive than with tape-based systems, causing a dramatic reduction in your investment in primary storage and power costs.

Getting data to this archive can be as simple as using an operating systems move command to get the data to it. In our next entry we will look at a new technique, an optimized move.

View our Webcast on Primary Storage Optimization to learn more.

Track us on Twitter: http://twitter.com/storageswiss.

Subscribe to our RSS feed.

George Crump is founder of Storage Switzerland, an analyst firm focused on the virtualization and storage marketplaces. It provides strategic consulting and analysis to storage users, suppliers, and integrators. An industry veteran of more than 25 years, Crump has held engineering and sales positions at various IT industry manufacturers and integrators. Prior to Storage Switzerland, he was CTO at one of the nation's largest integrators.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links