6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

Chapter 2: Disaster RecoveryPlanning for a Disaster What: No more than one hour of transaction data may be lost. Why: The cost is 1,000 transactions per hour of lost transactions that are enteredin R/3 and cannot be recreated from memory.This inability to recreate lost transactions may result in lost sales and upsetcustomers. If the lost orders are those that the customer quickly needs, thissituation can be critical. What: The system cannot be offline for more than three hours. Why: The cost (an average of $25,000 per hour) is the inability to book sales. What: In the event of disaster, such as the loss of the building containing the R/3data center, the company can only tolerate a two-day downtime. Why: At that point, permanent customer loss begins. Other: There must be an alternate method of continuing business.Ask yourself the following questions: What criteria constitute a disaster? Have these criteria been met? Who needs to be consulted?The person must be aware of the effect of the disaster on the company’s business and thecritical nature of the recovery.Expected downtime is only part of the business cost of disaster recovery. For definedscenarios, this cost is the expected minimum time before R/3 can be productive again.Downtime may mean that no orders can be processed and no products shipped.Management must approve this cost, so it is important that they understand that downtimeare potential business costs.To help business continue, it is important to find out if there are alternate processes that canbe used while the R/3 System is being recovered.System Administration Made Easy2–5