6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

Chapter 2: Disaster RecoveryPlanning for a DisasterThere are an infinite number of disaster scenarios that could occur. It would take an infiniteamount of time to plan for them, and you will never account for all of them. To make thistask manageable, you should plan for at least three and no more than five scenarios. In theevent of a disaster, you would adapt the closest scenario(s) to the actual disaster.The disaster scenarios are made up of: Description of the disaster event High level plan of major tasks to be performed Estimated time to have the system available to the usersTo create your final scenario:1. Use the Three Common Disaster Scenarios section below as a starting point.2. Prepare three to five scenarios that cover a wide range of disasters that would apply toyou.3. Create a high-level plan (are made up of major tasks) for each scenario.4. Test the planned scenario, by creating different test disasters and determining if (andhow) your scenario(s) would adapt to an actual disaster.5. If the test scenario(s) cannot be adapted, modify or develop more scenarios6. Repeat the process.The following three examples range from a best-to-worst scenario order:The downtimes in the examples below are only samples. Your downtimes will be different.You must replace the sample downtimes with the downtimes applicable to yourenvironment. A corrupt database could result from: Accidentally loading test data into the production system. A bad transport into production, which results in the failure of the productionsystem. Such a disaster requires the recovery of the R/3 database and related operating systemfiles. The “sample” downtime is eight hours. The following types of items may fail: A system processor A drive controller2–8Release 4.6 A/B