Commentary

Howard Marks
 

Continuity's RecoveryGuard Reveals DR Flaws

Today's large IT environments are dynamic places; applications, volumes, and file systems are added, deleted, and reallocated on SANs on a daily basis. The disaster recovery plan, on the other hand, is updated and tested on an annual basis. As a result, most organizations think their data is better protected than it really is.

Today's large IT environments are dynamic places; applications, volumes, and file systems are added, deleted, and reallocated on SANs on a daily basis. The disaster recovery plan, on the other hand, is updated and tested on an annual basis. As a result, most organizations think their data is better protected than it really is.If the Oracle DBAs say they need another 1TB LUN (logical disk), a storage administrator may skip step 19 in the official provisioning process that says to add the new LUN, and it's doppelganger at the DR site to the replication regime. When each management group looks in their management consoles, everything looks hunky dory.

Continuity Software's RecoveryGuard discovers the Oracle database, which LUNs it's using, and how they're replicating, and raises the red flag that the Oracle database isn't as protected as we thought it was. RecoveryGuard can investigate Oracle, Sybase, and MS SQL Server databases, and EMC's SRDF and Network Appliance SNAPmirror replication.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Continuity Software offers a free 48-hour evaluation and a spokesman told me that they have found at least one gap in the data protection at every company that's taken advantage of the offer. Since in our recent survey almost 60% the respondents indicated that they failed to recover at least one of their important applications in their last DR test, I can believe it.

Right now, RecoveryGuard is for the big boys with EMC and NetApp infrastructures that don't mind paying $2,000/protected server/a year to avoid multimillion dollar data losses. For them, it could be a bargain.


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