So the place to begin defining your disaster recovery plan is not in the server room but rather out among the business units. For example, maybe you work for a financial institution that has to comply with Sarbanes_Oxley, HIPAA or PATRIOT Act regulations. Information availability is required under all conditions, including routine back_up. Fines for non_compliance and damage to reputation for failure to comply are huge. Or Your organization manufactures precision electronic components and your ERP and inventory management systems must be operational during the week. Downtime costs you /hour. However, routine maintenance can be performed during the week. Or Your company processes a high volume of data entry, fulfillment processing and shipping operations around the clock. Downtime has been calculated to be ผ꺜 per hour.
Different scenarios with 3 entirely different sets of requirements. Hopefully you see that before you can develop or use a recovery plan template for your organization you must identify, understand, and prioritize the requirements of each of the most critical processes.