When a disaster strikes are you going to be ready? If you can’t answer this question with 100% surety then you have a challenge in front of you. There are many different plans to prepare yourself for a disaster. One that I have seen used both in the public sector in the United States and the private sector is the National Incident Management System (NIMS) and more specifically the Incident Command System (ICS). These have been developed over the last 20 years to help agencies in the United States respond to a disaster. There are similar systems available in almost every country and region around the world.
While both of these programs have been developed to respond to a public disaster – typically a natural disaster – they provide a very good foundation for the complete disaster management cycle.
ICS breaks the process down into 4 discreet components: Mitigation, Preparedness, Response and Recovery. On PSDN, Marv Stone and I will do a webinar / podcast on these components and how OpenEdge 10 meets these needs for your application.
Mitigation deals with identifying requirements (business and safety for example) and minimizing or avoiding those risks altogether. An important part of this process is identifying where you are vulnerable. Once you have identified this you can start to figure out what you “really” need to worry about. This moves right into the planning component of your Disaster Recovery plan.
Planning addresses what options are available, choosing the appropriate option to meet your needs, implementing that option and testing the plan. This is one of the most critical components in the process. It also takes the most time. It is an iterative process and will never be done…
The next component is Response. This is execution of the plan. The first part of this is declaring the disaster. This would seem like a simple thing to do, but it isn’t. I will talk about this in my next blog. This is where your testing with your solution will pay off. Whether it’s OpenEdge Replication, Failover Clusters, or After-Imaging, if you haven’t tested thoroughly then this could turn into a nightmare. A critical part of this process is documentation. Documenting what is being done, who is doing it, and when it was done is critical to the post-mortem (or Recovery) component of your environment. If you don’t document and learn from your mistakes, you will inevitably make them again.
The last component is Recovery. This can be interpreted in several different ways. In the public sector it revolves around returning to life as usual (or as usual as it can possibly be). In the private sector it involves failing back to your production environment and getting the complete business back up in business as usual mode. This is also affected by your planning process. Failing back should be planned and tested in the Planning component of your plan. Documentation is also critical in this component in order to clean up and prevent additional outage time.
Marv and I will chat about these and where OpenEdge 10 plays a part in all of these components of your Disaster Recovery plan. Be sure to listen in!
Until next time, a disaster is only a disaster if you are not ready for it.
Brian Bowman has been working for Progress for over 20 years. He has performed database tuning and disaster planning for all sizes of customers around the world. Brian started in technical support, and has also worked in product development, pre-sales for Direct and Indirect customers and is currently a Senior Principal Product Manager for OpenEdge.
Subscribe to get all the news, info and tutorials you need to build better business apps and sites
You have the right to request deletion of your Personal Information at any time.
You can also ask us not to pass your Personal Information to third parties here: Do Not Sell My Info
Let our experts teach you how to use Sitefinity's best-in-class features to deliver compelling digital experiences.
Copyright © 2021 Progress Software Corporation and/or its subsidiaries or affiliates.All Rights Reserved.
Progress, Telerik, Ipswitch, Chef and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.