[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-244931-105":53,"doc-detail-244931-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","banner-disaster-recovery-plan-comprehensive-drp","Banner Disaster Recovery Plan - Comprehensive DRP","","Banner Disaster Recovery Plan defines comprehensive procedures to quickly restore Banner services after a disruption, protecting mission-critical Ventura County Community College District processes. It covers objectives for activation and notification, recovery restoration, and reconstitution through validated testing before resuming normal operations. The plan targets recovery within 3 hours for a high-impact Banner system, states scope and assumptions about AWS us-west-2 sites, and excludes equipment replacement and short disruptions under 3 hours.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":41,"@type":70,"position":76},"https://docshare.wps.com/template/letters/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/banner-disaster-recovery-plan-comprehensive-drp/244931/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/banner-disaster-recovery-plan-comprehensive-drp/244931.png","ImageObject",442,249,{"name":88,"@type":89},"Rowan","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-19","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",8,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What is the primary purpose of the Banner Disaster Recovery Plan?","Question",{"text":109,"@type":110},"It establishes comprehensive procedures to recover Banner quickly and effectively after a service disruption, minimizing excessive interruption to mission/business processes.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What recovery timelines and priorities does the plan set?",{"text":114,"@type":110},"The plan is designed for high-impact systems and targets recovery of Banner within 3 hours. It prioritizes timely recovery because system unavailability affects services to students and the public.",{"name":116,"@type":107,"acceptedAnswer":117},"What environments and AWS locations are referenced in the plan’s scope and assumptions?",{"text":118,"@type":110},"The primary production site and offsite storage are in AWS us-west-2 (AZ1), while alternate processing sites and offsite storage are in us-west-2 (AZ2). A development server hosts test, devl, and the DR system databases with continuous replication via Oracle Data Guard.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},244931,1789223180,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":40,"category_name":41,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":136,"language":137,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":61,"update_tm":126,"read_time":141},1099514067415,"https://ap-avatar.wpscdn.com/avatar/100002539d78ffe74a7?x-image-process=image/resize,m_fixed,w_180,h_180&k=1779092875211072502","Banner Disaster Recovery Plan  \nTable of Contents  \n􀁸  1. Introduction  \n􀁸  2. Concept of Operations  \n􀁸  3. Activation and Notification  \n􀁸  4. Recovery  \n􀁸  5. Reconstitution  \n􀁸 Appendix A: Personnel Contact List  \no  Banner DRP Key Personnel  \no  Banner DRP Key College Contacts  \no  Banner Functional Testing Key Personnel  \n􀁸 Appendix B: Vendor Contact List  \no  Open a support ticket with Ellucian  \no  Open a support ticket in Oracle  \n􀁸 Appendix C: Detailed Recovery Procedures (Run Book)  \no  1. Verify integrity of AD Domain Controller in AZ2 .  \no  2. Restore Banner Components from Backups  \n􀂃  On-prem restore  \n􀂃  Web UI restore  \n􀂃  Bastion host restore  \no  3. Verify Oracle database data replication status and DB availability in AZ2  \no  4. Recover Banner Job Submission Server (EC2)  \no  5. Verify integrity of EFS shared file system in AZ2  \no  6. Update internal DNS entries for the Database  \no  7. Verify integrity of PortalGuard IDP (Database and Front End Webserver)  \no  8. Verify ECS cluster is running and each application is functional  \no  9. Recover reporting and integration EC2 server instances from Veeam backup  \no  10. Verify nightly processing jobs are working correctly  \n􀁸 Appendix D: Alternate Processing Procedures  \n􀁸 Appendix E: System Validation Test Plan  \n􀁸 Appendix F: Diagrams (System and Input/Output)  \n􀁸 Appendix G: AWS Resources Inventory  \n􀁸 Appendix H: Interconnections Table  \n􀁸 Appendix I: Test and Maintenance Schedule  \n􀁸 Appendix J: Business Impact Analysis  \n􀁸 Appendix K: Banner Disaster Recovery Event Documentation  \no  TEMPLATE: MM/DD/YYYY-Disaster recovery event  \n􀁸 Appendix L: Banner Disaster Recovery Functional Test Documentation  \no  TEMPLATE: MM/DD/YYYY-Disaster recovery functional test  \n􀁸 Appendix M: Version Info and Changes  \nCopyrights and Trademarks are the property of the respective owners for any products mentioned herein.  \nJump to Appendix C: Detailed Recovery Procedures (Run Book)  \n1. Introduction  \nInformation systems are vital to the Ventura County Community College District  \nmission/business processes; therefore, it is critical that services provided by Banner © can operate effectively without excessive interruption. This Disaster Recovery Plan (DRP) establishes comprehensive procedures to recover Banner quickly and effectively following a service disruption.  \n1.1 Background  \nThis Banner DRP establishes procedures to recover Banner following a disruption.  \nThe following recovery plan objectives have been established:  \n􀁸 Maximize the effectiveness of contingency operations through an established plan that consists of the following phases:  \no Activation and Notification phase to activate the plan and determine the extent of damage  \no Recovery phase to restore Banner operations  \no Reconstitution phase to ensure that Banner is validated through testing and that normal operations are resumed.  \n􀁸 Identify the activities, resources, and procedures to carry out Banner processing requirements during prolonged interruptions to normal operations.  \n􀁸 Assign responsibilities to designated COS personnel and provide guidance for recovering Banner during prolonged periods of interruption to normal operations.  \n􀁸 Ensure coordination with other personnel responsible for COS contingency planning strategies. Ensure coordination with external points of contact and vendors associated with Banner and execution of this plan.  \n1.2 Scope  \nThis DRP has been developed for Banner, which is classified as a high-impact system. Procedures in this DRP are for high-impact systems and designed to recover Banner within 3 hours. This plan does not address replacement or purchase of new equipment, short-term disruptions lasting less than 3 hours, or loss of data at the onsite facility or at the user-desktop levels.  \nThe following assumptions were used when developing this DRP:  \n􀁸 Banner has been established as a high-impact system.  \n􀁸 Recovery of Banner in a timely manner is a very high prio","cbCaihhHWjQXlkaV","https://ap.wps.com/l/cbCaihhHWjQXlkaV","pdf",3174013,122,"English","# 1. Introduction\n## 1.1 Background\n## 1.2 Scope\n# 2. Concept of Operations\n# 3. Activation and Notification\n# 4. Recovery\n# 5. Reconstitution\n# Appendix A: Personnel Contact List\n# Appendix B: Vendor Contact List\n# Appendix C: Detailed Recovery Procedures (Run Book)\n# Appendix D: Alternate Processing Procedures\n# Appendix E: System Validation Test Plan\n# Appendix F: Diagrams (System and Input/Output)\n# Appendix G: AWS Resources Inventory\n# Appendix H: Interconnections Table\n# Appendix I: Test and Maintenance Schedule\n# Appendix J: Business Impact Analysis\n# Appendix K: Banner Disaster Recovery Event Documentation\n# Appendix L: Banner Disaster Recovery Functional Test Documentation\n# Appendix M: Version Info and Changes","[{\"question\":\"What is the primary purpose of the Banner Disaster Recovery Plan?\",\"answer\":\"It establishes comprehensive procedures to recover Banner quickly and effectively after a service disruption, minimizing excessive interruption to mission/business processes.\"},{\"question\":\"What recovery timelines and priorities does the plan set?\",\"answer\":\"The plan is designed for high-impact systems and targets recovery of Banner within 3 hours. It prioritizes timely recovery because system unavailability affects services to students and the public.\"},{\"question\":\"What environments and AWS locations are referenced in the plan’s scope and assumptions?\",\"answer\":\"The primary production site and offsite storage are in AWS us-west-2 (AZ1), while alternate processing sites and offsite storage are in us-west-2 (AZ2). A development server hosts test, devl, and the DR system databases with continuous replication via Oracle Data Guard.\"}]","Banner Disaster Recovery Plan - Comprehensive DRP | PDF",43]