Are you looking for place to read full E-Books without downloading? You can also read and download new and old full E-Books. DOWNLOAD THIS BOOK FOR FREE
Many organizations depend on the 24/7 availability of their mission critical IT systems. A lot of work goes into managing the on-going requirements for these systems. And when you have downtime, it can be extraordinarily painful for your business. When business stops, it can get quite expensive in a hurry for you and your customers. Having a comprehensive disaster recovery plan is crucial to assuring success for any business these days. In fact, your most astute customers may even require it.
A quick search on the Internet will direct you to a myriad of organizations, tools and technologies ready to help you establish your disaster recovery plan/business continuity plan (DRP/BCP). While the concept of DRP/BCP has been around for nearly 40 years, many companies find themselves coming up short in DRP/BCP despite their increased dependence on IT systems. Businesses typically agree that they want a disaster recovery solution. However many are daunted by the high cost to setup and maintain an "always ready" disaster recovery site. The complexities and costs of a DRP/BCP solution historically have caused businesses to cut corners or risk no planning whatsoever.
DISASTER RECOVERY PLANNING BASICS
Disaster recovery planning (DRP) is often considered a component or subset of business continuity planning (BCP). Disaster recovery generally refers to the processes and procedures used to recover after a disruptive event. It often focuses around the critical IT systems within an organization. Business continuity planning usually includes the business functions that need to continue after a disruption so your business continues to make money.
At a high level, disaster recovery planning usually involves the following steps:
Identify the scopes and boundaries - This is typically the first step towards completing your disaster recovery plan. Identifying the scope involves prioritizing the critical systems for disaster recovery and assigning a value to the failures of those systems. This is also the phase in which you determine the RTO (recovery time objective) and RPO (recovery point objective) requirements from the business units for critical applications.
Establish the Budget - Budgeting for disaster recovery plans can be tricky. Often you will want to do an assessment of the costs to the business of suffering different disaster scenarios. Comparing different options for recovery can vary the costs of the disaster recovery plan. Reducing RPO and RTO requirements can soften the financial costs of the disaster recovery plan. But you should be realistic and ensure executive management understands the risks of data loss and system availability being stretched out. Both IT and executive management must come to an agreement on the budget and IT will work within the constraints of the budget that has been established.
Develop and Deploy the Plan - Developing and deploying the plan can be the most involved part of this process. Often the plan is actually a "script" of activities that occur in order and are executed by a recovery team made up of resources from IT. Roles and responsibilities are assigned in the plan as well. Deploying the plan involves choosing the tools and technologies needed to meet the RTO and RPO requirements established in the first step while still working within the constraints of the budget.
Test - Test, test, test. Disaster recovery plans are simply not effective if they are not properly and frequently tested. Test the systems you're going to use in recovery regularly to validate that all the pieces work. Always record your test results and update the disaster recovery plan to address any shortcomings. As your business environment changes, so should your disaster recovery plan. .Are you looking full ebook about this topicGet Full Ebook For This Article
