Planning for Disaster

by Rudy P
The article I am blogging about this week is titled, ” Disaster Preparedness: Planning Ahead” written by Samara Lynn from This article attempt to give a few suggestions of planning for a disaster, and really attempts to stressing the planning phases importance. The article gives an example of an earthquake doing damage to a database server, and states without prior planning, IT may be “scrambling to find a place to set up a replacement server, take a copy of the data and applications from the damaged server, and then restore that data and re-install mission-critical apps to give end-users the alternative access they need to continue key operations” (Lynn 2012). The author states a disaster preparation plan must be able to keep data and apps required for day to day operations, running in a remote location, and ready to be accessed. The author gives a 3 steps for a company to be prepared for a disaster. The company should think about and prepare for disasters most likely to affect the immediate area, such as a hurricane hitting a location near the coast. Determine how said disasters would impacts an IT infrastructure and system. The company should also have inner department meetings in order to keep the non IT departments involved in the planning. Today, disaster preparedness is easier than ever to deploy because of technological advances such as cloud computing, virtualization and the increasing power of mobile/portable devices.

I chose this article because it seemed interesting to be, especially with the recent natural disaster that hit the east coast. While in my 307 course, Professor Lopez spoke about the site for our text book going down and remained down after the hurricane hit the coast. This is surly the result of a poor disaster preparation plan, and the lack of a back up in a remote location away from the disaster. For a company that sells books nation wide and has many school professors relying on the information on their site, this seems surprising. However, the article mentions a recent survey conducted by Symantec of IT decision-makers in small- to-mid-sized businesses, where only 26% of them had a disaster preparedness plan in place.

These results as a whole were shocking to be, because how much easier these plans are becoming to deploy from a technology stand point. This lack of a plan could be for various reasons, such as economic, however losing a large amount of data or even customers would be much more costly. This article relates to the topic of database administration and data back up in the chapter we had recently covered. I believe it would be the database administrator that would be directly involved with this planning and preparation in an organization.

Source: Lynn, S.(2012, August 7). Disaster Preparedness: Planning Ahead. Retrieved December 2, 2012, from,2817,2408092,00.asp



4 thoughts on “Planning for Disaster

  • December 2, 2012 at 4:49 pm

    Great article! I believe we all do need to plan ahead and be prepared for any sort of disasters. Of course, there is no exception for data. Especially, data nowadays plays an important role for any business units. Ones should never take any chance of losing something that is important to oneself. Recalling from one of my post about Amazon’s Glacier Cloud Service, which data stored in the availability area is backed up to two facilities in addition to its primary location. In spite of the fair price of the service, the guaranteed protection alone has already got people attention when comparing to other competitors’ offer.

  • December 2, 2012 at 8:25 pm

    Interesting Article Rudy, I too am in your 307 telecommunications class and i must admit that incident inspired my answer for the in class excercise we participated in which stated that I would have at least 2 different server locations that synched up with the cloud in different parts of the world or country dealing with hopefully none or minimal natural disasters. If I was really running my own company I would most certainly not just have one place where I would keep my entire database at, hopefully the textbook company learns from their mistakes and better prepare for the future.

  • December 2, 2012 at 11:08 pm

    Your article is really relevant to the recent chapter. It is a good example of what a DBA most likely has to deal with since management of small-mid sized businesses probably have database recovery plans at the bottom of their to do list because of budget constraints. I read an article earlier this quarter on eBay’s “trailer-park” data center in Phoenix, Arizona. These prefabricated containerized data centers operated on top of computing centers in 110+ degree weather. It allows for storage to be easily added to the data center, so businesses can just purchase storage as needed with availability for expansion. Containerized data centers are in its early stages, so small to mid sized businesses probably won’t be able to afford them now but the article says that research reports predict a 40% growth in their market. Therefore time, technological advancement, and economies of scale may make this a feasible option. The article by Klint Finley (2012) in which I referenced is at

  • December 3, 2012 at 1:20 am

    Good read, negligence of back up will cause great consequence in future. I myself recently broke my laptop, and I did not back up anything. I knew I should back up regularly, but I was too lazy to do so. In result, I lost all my data. Like we learned in lecture, in business world, it is more important to back up regularly. I recently found a great tool that helps us back up without hardware, called “could backup” you can find more information at if you want.

Comments are closed.