[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-241842-105":3,"detail-sidebar-cat-1-en-105":81,"doc-detail-241842-en":127},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","it-disaster-recovery-plan-template-development-guide","IT Disaster Recovery Plan Template - Development Guide","","IT disaster recovery plan template covering scope and size, disaster definitions, and a complete technical framework across hardware/software, environmental setup, customers and applications, staffing, and networking. It details administrative and logistical processes, including how to detect disasters, classify outage scenarios, and document asset inventory, change control, and problem tracking. The plan emphasizes testing, training, ongoing maintenance, and practical implementation constraints such as budget limits, business continuity alignment, and campus crisis integration.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/forms/","Forms",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/it-disaster-recovery-plan-template-development-guide/241842/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/it-disaster-recovery-plan-template-development-guide/241842.png","ImageObject",442,249,{"name":42,"@type":43},"McGucket","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-12","2026-09-12",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",7,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What should be agreed to determine the scope and size of an IT disaster recovery plan?","Question",{"text":63,"@type":64},"The plan’s scope level should be agreed, and it should be practical and understandable for non-IT stakeholders. It should align with any overarching campus crisis plan and include the master data center recovery plan.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"How does the template define a “disaster” for DR planning purposes?",{"text":68,"@type":64},"It lists criteria across physical, data, and hardware aspects and guides how to confirm detection. It also distinguishes examples like outages by hours, loss of a data center, loss of core services such as email, and escalating threats that grow into disasters.",{"name":70,"@type":61,"acceptedAnswer":71},"Which technical and environmental elements are covered in the DR framework design?",{"text":72,"@type":64},"It covers hardware/software considerations such as vendor models, asset inventory, change information systems, tracking issues, redundancy, backups, storage, and enterprise systems. Environment design includes one vs. multiple data centers, hot/warm/cold site options, and safety and security measures like re-entry procedures and alternate power sources.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},241842,1789181895,{"code":4,"msg":82,"data":83},"success",[84,89,94,99,104,109,113,118,123],{"id":85,"doc_module":22,"doc_module_name":25,"category_name":86,"show_sort_weight":87,"slug":88},11,"Presentations",90,"presentations",{"id":90,"doc_module":22,"doc_module_name":25,"category_name":91,"show_sort_weight":92,"slug":93},12,"Resumes",80,"resumes",{"id":95,"doc_module":22,"doc_module_name":25,"category_name":96,"show_sort_weight":97,"slug":98},14,"Invoices",70,"invoices",{"id":100,"doc_module":22,"doc_module_name":25,"category_name":101,"show_sort_weight":102,"slug":103},15,"Posters",60,"posters",{"id":105,"doc_module":22,"doc_module_name":25,"category_name":106,"show_sort_weight":107,"slug":108},16,"Social Media",50,"social-media",{"id":110,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":111,"slug":112},17,40,"forms",{"id":114,"doc_module":22,"doc_module_name":25,"category_name":115,"show_sort_weight":116,"slug":117},18,"Letters",30,"letters",{"id":119,"doc_module":22,"doc_module_name":25,"category_name":120,"show_sort_weight":121,"slug":122},21,"Paper Templates",5,"papers-templates",{"id":124,"doc_module":22,"doc_module_name":25,"category_name":125,"show_sort_weight":4,"slug":126},158,"General","general-158",{"code":4,"msg":82,"data":128},{"doc_id":79,"user_id":129,"nickname":42,"user_avatar":130,"doc_module":22,"category_id":110,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":55,"language":136,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":12,"update_tm":80,"read_time":30},1236954412713,"https://us-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","IT Disaster Recovery Plan Template  \nCONTENTS:  \nSection 1: Determine Scope and Size of DR Plan  \nSection 2: Definitions of Disaster  \nSection 3: Framework Design/Hardware and Software  \nSection 4: Framework Design/Environmental  \nSection 5: Framework Design/Customers and Applications  \nSection 6: Framework Design/Labor Resources  \nSection 7: Framework Design/Networking  \nSection 8: Framework Design/Cultural, Political, Financial  \nSection 9: Administrative Processes  \nSection 10: Logistical Processes  \nSection 11: Testing Processes  \nSection 12: Training Processes  \nSection 13: Maintenance of plan  \nSection 1--Scope and Size of Disaster Recovery Plan  \nA. Over-arching considerations  \n􀁸 Campus issues and checks:  \n􀂃 Records management requirements by individual state  \n􀂃 Requirement for business continuity plan (Definition: Business continuity plan is a customer’s plan to delivery service “manually” while IT disaster recovery restores electronic service.)  \n􀂃 HIPAA requires a disaster recovery plan  \n􀂃 University is a “business” and there is a big loss to the student when business is out of order.  \n􀂃 Do we need a business continuity plan for the students?  \n􀂃 Need to be practical and usable, not just theoretical  \n􀂃 Need to be understandable  \n􀂃 Can’t spend a lot of money  \nB. Determine Scope and Size  \n􀁸 Agree upon level of scope  \n􀁸 Can a “non-IT shop” person come in and understand the plan?  \n􀁸 Is the plan practical?  \n􀁸 Do we outsource the plan?  \n􀁸 Need to share examples  \n􀁸 Need to consider in overarching Campus crisis plan  \n􀂃 Within this, need to include master data center recovery plan  \n􀂃 Within this, need to include respective customer and individual service plans, e.g., PeopleSoft services, Mainframe services, enterprise storage services, individual customers’ computers, etc.  \nSection 2--Definitions of Disaster  \nA. What are (and what are not) the criteria to determine a disaster?  \n􀁸 Physical, data, hardware  \n􀁸 How do we know ifa disaster has been detected?  \nB. Examples ofa disaster  \n􀁸 Outage by hours  \n􀁸 Outage by hours greater than certain level requiring contact of disaster team to declare disaster (for ex., notify campus crisis team)  \n􀁸 When day-to-day plans no longer work (i.e., day-to-day work drill is gone, or when there is a build-up, escalation procedures are exhausted, and operation no longer meets common baseline planning  \n􀁸 When there are threats that scope up to become a disaster (i.e., Sept. 11, campus unrest, etc.)  \n􀁸 When we lose a data center or building that houses the data center  \n􀁸 When we lose complete staff (labor resources) of data center  \n􀁸 When we lose a core business service (i.e., email)  \n􀁸 When we require Risk Mgmt and Insurance to declare a disaster in order to get vendor action in recovery  \n􀁸 Need to share other examples of disaster in order to clarify for your own institution  \n􀁸 Need to develop own definitions of disaster that are practical as opposed to industry definitions.  \nSection 3--Framework Design: Hardware and Software  \nA. Who is the vendor?  \n􀁸 Proprietary (Sun Solaris, Linux, windows, AIX)  \n􀁸 Homegrown (you are the vendor)  \n􀁸 Mainframes  \n􀁸 Needs Service Level Agreements (SLA) with vendors to replace the equipment if disaster strikes  \nB. Hardware configured environments (i.e., production, test, crash and burn, etc.)  \nC. What is your hardware asset inventory? (Let’s share the data elements we are keeping about your assets.)  \n􀁸 i.e.,“Assets Center” by Peregrine; “LDR Plus” by Vendor?; Oracle database/homegrown systems (i.e., SOAPI)  \n􀁸 Damage assessment by Risk management and insurance  \n􀁸 Photos of equipment  \n􀁸 Naming conventions ofthe hardware  \nD. Change information system (how do you make changes to your hardware environment?)  \nE. Tracking system for problems with hardware, applications, and network  \nF. Categories of operating system software  \nG. Proprietary factors of software  \nH. Redundancy of data  \nI. Backing up the software, data and OS  \nJ.","cbCaigj143QY3PDe","https://ap.wps.com/l/cbCaigj143QY3PDe","pdf",145587,"English","# Section 1: Determine Scope and Size of DR Plan\n## Over-arching considerations\n## Determine Scope and Size\n# Section 2: Definitions of Disaster\n## Criteria to determine a disaster\n## Examples of a disaster\n# Section 3: Framework Design - Hardware and Software\n## Vendor, environments, and asset inventory\n## Change tracking and backups\n# Section 4: Framework Design - Environmental\n## Data center sites and site types\n## Physical security and safety systems\n# Section 5: Framework Design - Customers and Applications\n## Business continuity and impact analysis\n## Customer application priorities","[{\"question\":\"What should be agreed to determine the scope and size of an IT disaster recovery plan?\",\"answer\":\"The plan’s scope level should be agreed, and it should be practical and understandable for non-IT stakeholders. It should align with any overarching campus crisis plan and include the master data center recovery plan.\"},{\"question\":\"How does the template define a “disaster” for DR planning purposes?\",\"answer\":\"It lists criteria across physical, data, and hardware aspects and guides how to confirm detection. It also distinguishes examples like outages by hours, loss of a data center, loss of core services such as email, and escalating threats that grow into disasters.\"},{\"question\":\"Which technical and environmental elements are covered in the DR framework design?\",\"answer\":\"It covers hardware/software considerations such as vendor models, asset inventory, change information systems, tracking issues, redundancy, backups, storage, and enterprise systems. Environment design includes one vs. multiple data centers, hot/warm/cold site options, and safety and security measures like re-entry procedures and alternate power sources.\"}]","IT Disaster Recovery Plan Template - Development Guide | PDF"]