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.


12:16 PM
George Crump
George Crump

Survived Ike? Time Will Tell...

Ike tore through Houston, home one of our office and our lab. Once again, businesses have to learn that surviving the initial hit is only the beginning. The "P" part of a Disaster Recovery Plan is very critical to the long-term survival of the business.

Ike tore through Houston, home one of our office and our lab. Once again, businesses have to learn that surviving the initial hit is only the beginning. The "P" part of a Disaster Recovery Plan is very critical to the long-term survival of the business.About half our team and our lab happens to be in Houston. Everyone on our team there is safe and, while we avoided the hard hit that Galveston and the south sides of Houston received from Hurricane Ike, our lab is without power, as are many Houston-area businesses, and we are being told that it will be that way for weeks.

We, like hopefully most businesses, have our data stored on disaster-proof hard drives as well as replicated out to our Dallas office (where I safely rode out the storm). For businesses in the greater Houston area, that "P" part of Disaster Recovery Planning is now being tested. So much work is spent on getting the data out, and even doing testing, but often DR tests are a "pass/fail" sort of occurrence. It looks like Ike is going to be a longer-term situation.

We have all heard the stats of businesses that go out of business after a major disaster. Many times, while the disaster shuts the doors, it's the prolonged time away that puts the lock on the doors. So after the obvious first step of getting the data out of the facility, one that I and countless others have written about, comes living with the DR sites capabilities.

Having the data safe is only half the battle. Doing something with that data, and for a prolonged period of time, is the other half. Here are some challenges of users that I am talking to.

• First, a common mistake is not getting the data far enough away or not having your DR location far enough away. Right now, much of Houston is without power, and except for facilities that have generators, it's possible that both your primary and your DR site may be down.

• Second, many businesses replicated to a cheaper, possibly less reliable and lower performing, storage system. There is serious concern about running mission-critical apps on these systems for the next few weeks. When you are designing your disaster recovery environment, make sure you have storage in the remote location suitable to sustain the performance and reliability that your applications demand.

• Third, some customers "over-virtualized" their DR site. One of server virtualization's big appeals is to be able to put less hardware in the DR site by virtualizing much of the server environment in the DR location. Is the virtual infrastructure able to sustain operations for a few weeks or will that environment be over-burdened? This morning, customers are scrambling to order additional hardware to spread out this load. As part of your DR testing, make sure you don't overburden the DR servers and make sure you know who to call to quickly bring up another virtualization host and distribute that load.

• Fourth, there are many instances of no backup at the DR site! The DR site just became production for many businesses and when it did that, it now needs protection. There are many sites running right now without the safety net of a backup. As part of your planning, make sure you keep the backup capability current with the needs of the DR site. Also make sure you have the ability to replicate data out of your DR site to another site, just in case you're unlucky enough to have a problem at your DR site, too.

One of the critical elements in disaster planning is to plan for a long-term activation of your DR site. Always factor in at least four weeks of remote operation and make sure your DR site is designed to handle that workload.

• The final step is planning for failback. One of the most challenging steps, and typically the least planned or tested, is the failback, the process of returning production to its original location after a disaster. We'll discuss that next entry.

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.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
6 Small-Business Password Managers
Curtis Franklin Jr., Senior Editor at Dark Reading,  11/8/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  11/13/2019
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2019-11-14
fs/btrfs/volumes.c in the Linux kernel before 5.1 allows a btrfs_verify_dev_extents NULL pointer dereference via a crafted btrfs image because fs_devices->devices is mishandled within find_device, aka CID-09ba3bc9dd15.
PUBLISHED: 2019-11-14
Scanguard through 2019-11-12 on Windows has Insecure Permissions for the installation directory, leading to privilege escalation via a Trojan horse executable file.
PUBLISHED: 2019-11-14
Microstrategy Library in MicroStrategy before 2019 before 11.1.3 has reflected XSS.
PUBLISHED: 2019-11-14
STMicroelectronics ST33TPHF2ESPI TPM devices before 2019-09-12 allow attackers to extract the ECDSA private key via a side-channel timing attack because ECDSA scalar multiplication is mishandled, aka TPM-FAIL.
PUBLISHED: 2019-11-14
SnowHaze before 2.6.6 is sometimes too late to honor a per-site JavaScript blocking setting, which leads to unintended JavaScript execution via a chain of webpage redirections targeted to the user's browser configuration.