Why Continuous Data Protection's Getting More Practical

Lower costs are putting it within reach of more companies.

InformationWeek Green - May 10, 2010 InformationWeek Green
Download the entire May 10, 2010 issue of InformationWeek, distributed in an all-digital format as part of our Green Initiative
(Registration required.)
We will plant a tree
for each of the first 5,000 downloads.

Why Continuous Data Protection's Getting More Practical Companies are moving away from traditional tape- or even disk-based backups that can come with recovery times measured by a calendar instead of a stopwatch. An increasing number are turning to data replication and continuous data protection, letting them bounce back from a disaster in hours and, in some cases, even minutes.

Replicating data locally or across the WAN to a disaster recovery site in real time isn't new--companies with the big bucks to implement it have been doing this for years. What has changed in the last few years is that this higher level of protection is increasingly affordable and accessible to more companies; it's now well within the reach of small businesses.


More Services Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Lower initial costs for hardware, software, and services are making continuous data protection more affordable, as are technologies and services that significantly lower ongoing monthly charges. These include everything that makes it more efficient to send data across the wire, from compression and deduplication to WAN optimization.

Technologies such as compression and deduplication can decrease data traffic and significantly reduce bandwidth requirements and overall costs. While deduplication and compression allow more efficient use of available bandwidth, bandwidth itself is becoming cheaper--yet another driver in increasing the affordability of these options. Better and cheaper WAN acceleration products and technologies are also playing a role by allowing much more efficient use of available bandwidth. That enables replication across a smaller and lower-cost link. It also may allow faster recovery from a problem.

But replication has a dark side as well. If you have corruption in data at your primary site--due to hardware or software problems, user error, or other problems--you might replicate that corruption to the secondary site as well. That's not what you're looking for from a disaster recovery system. You need something that protects against that corruption, and that's where continuous data protection, or CDP, comes in.

What is CDP? There's some disagreement as to what qualifies as true CDP and what may be more appropriately called "near CDP." The CDP group within the Storage Networking Industry Association defines it as continuously capturing or tracking "data modifications and stores changes independently of the primary data, enabling recovery points from any point in the past." CDP systems may be block-, file-, or application-based.

To read the rest of the article,
Download the May 10, 2010 issue of InformationWeek


From Disaster Recovery to Continuous Data Protection

Our full report on business continuity, disaster recovery, and continuous data protection, is free for a limited time

This report includes 13 pages of action-oriented analysi including:

  • Analysis of options companies have for CDP and replication
  • Analysis of virtualization's role in CDP and disaster recovery
  • Example of how replication choices are changing around Exchange environments
Get This And All Our Reports


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