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

12/14/2010
11:30 AM
George Crump
George Crump
Commentary
50%
50%

What Disaster Are You Planning For?

When the subject of disaster recovery comes up many IT professionals' minds immediately flash to an epic event like a fire, hurricane, tornado or earthquake. While this is fine for a point of reference, what about planning for the more mundane disaster? These simple disasters can often cost you as much in revenue and brand reputation than their larger alternatives.

When the subject of disaster recovery comes up many IT professionals' minds immediately flash to an epic event like a fire, hurricane, tornado or earthquake. While this is fine for a point of reference, what about planning for the more mundane disaster? These simple disasters can often cost you as much in revenue and brand reputation than their larger alternatives.I have nothing against planning for a disaster that assumes the loss of the primary data center and moving operations to an alternate site. Clearly this is something you should plan for. The problem that I have seen is that when planning for these once in a lifetime disasters people often loose site of the risk involved in the once a month mini-disasters. Mini-disasters are situations that occur and impact a small section of your data center. It can be a double drive failure on a RAID array, application data getting corrupted or the server/virtual machine that the application runs on crashing for some reason.

As we will discuss in our upcoming webcast "What's Missing From Your DR Plan for 2011?" mini-disasters tend to get left out of most disaster plans and application rollout projects. Mini-disasters don't capture headlines, users have no idea in many cases why their application isn't available, they just start calling IT and asking when it will be fixed. Then they wait and there goes productivity. Lost user productivity can delay production which will impact revenue. The situation is worse when customers have no idea why they can no longer place an order or use a particular service. Customers don't wait for you to fix the problem, they just go somewhere else. These mini-disasters also send the IT staff into a wasteful fire-drill mode and put friction in the relationship between IT and the rest of the organization.

For these mini-disasters most IT pros count on the backup process to bring things back to life. Probably for many applications that is a fair expectation but even if all the back data is actually recoverable, there is a gap in how often that data has been protected and there is a time delay in how long it will take to restore that data back into place, especially if it needs to be copied across an Ethernet network. The net impact is that you should count on a minimum of four hours of downtime when recovering from a backup system. Server virtualization and virtualization specific backup applications can help, as can application availability applications. All of which we will cover in our upcoming entries.

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-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...