Project Management Pack Software Disaster Recovery Plan

Software Disaster Recovery Plan

View Document Sample
Document Length: 18 Pages

This document is found in the following products:
$197 Proposal Kit Pro
$97 Proposal Kit Web Freelancer

Category: Plans and Procedures

Usage:
Use the Software Disaster Recovery Plan to outline your company's policies and procedures in the event of a loss or damage to software assets. Outline a recovery plan for the continuity of the business and business operations which rely on software systems.

Related documents may be used in conjunction with this document depending on your situation. Many related documents are intended for use as part of a project management system.
Related Documents:
Disaster Recovery Plan

The Project Management Pack suite of templates compliments the proposal and contract documents by giving you a collection of business documents to be used once you have a project to work on.

Alternate and related documents are also listed if there are other templates similar in nature, on a different scale or which can be used to provide additional information.

A wide variety of documents are included and are intended to be picked based on your needs. All projects are different and have different needs and goals. Pick the collection of documents from our collection and use them as needed for your project. Recommendations and samples provided are only intended as general guidelines.

Project documents may also be referred to as a template, document, outline, boilerplate, letter, sample, form or example.

Additional search terms related to this document:

business, project, management, information, documents, templates, boilerplate, form, outline, text Software Disaster Recovery Plan SDRP THE SDRP PROJECT DOCUMENT TITLE Author Title Company CurrentDate Document Version Control Information Introduction Purpose this document Objectives Insert the purpose this document its objectives and its intended audience. Example The purpose this document formally recognize and codify the policies and procedures Company wishes enact order both safeguard the Company investment their Software and ensure that the event disaster the Company can minimize any interruption its businesses The Company recognizes that its Software important part its continued business operations and this plan provides Company Employees Staff and Vendors this Software Disaster Recovery Plan SDRP overview the required steps and policies enacted following emergency. Scope Document Insert description the scope this Software Disaster Recovery Plan Describe whether this covers the entire company specific business unit department and whether this plan shall governed supersedes other policy documents that may already place. Scope Constraints Insert constraints such schedules costs interactions overview any other information relevant the Software Disaster Recovery Plan. Goals this Plan Insert overview brief description the product software other desired end result that included this Software Disaster Recovery Plan. Business Context Insert overview the business organizations impacted this Software Disaster Recovery Plan Include the business organization critical components and reliance Software Note This section will primarily used set priorities and identify and classify risk the Company pertains recovery from Disaster Event. Goals Defined The Overall Goals the SDRP are provide easy and accessible methods for Company recover from any the following events occurrences. Loss installed software and applications Loss updates patches fixes other required upgrades Loss installation disks packages other media Loss software proof license ownership Loss software inventory software inventory data other DRM Digital Rights Management information. References and Reference Material Insert list all reference documents and other materials related the Software Disaster Recovery Plan References will often include but are not limited. Company Business Continuation Plan BCP Company Disaster Recovery Plan DRP Company Recovery Point Objectives RPO Company Recovery Time Objectives RTO Company Computer Use Policies Software Acquisition Plan Software Management Plan Documentation Items Insert references documentation including but not limited Software Requirements Specification SRS Software Design Specification SDS Software Development Plan SDP Software Installation Guides Software User Guides Software Features Guides Software Bug Error Correction Defect Removal Guides Plan Components Inventory Catalog and Control centralized Software Database and Control System SDCS for inventory shall maintained for all software licensed the Company Before new software can put into service must entered into the SDCS the department Regular audits employee computers will performed ensure compliance complete copy all SDCS data shall maintained off Company property and updated regular basis. Check Procedures Software shall undergo check procedure including all downloadable virtual online ASP hosted application forms All software regardless its form the media which delivered shall entered the SDCS This procedure subject change based the individual software licensing requirements however all software shall have record entry the SDCS regardless its physical form. Check shall include but not limited Providing proof purchase Providing proof license Providing proof Company license and not individual license Providing all installation disks media manuals and collateral materials Directing staff any online manuals and documentation Providing original downloads and installation files for all software and licenses delivered virtually. Providing copies all licenses serial numbers activation keys IDs passwords logins other information required run the software application. Submitting complete set information concerning the software you want license and install will ensure faster entry into the SDCS and approval for the use the software. Insert additional descriptions the tasks performed Inventory Audits Company shall conduct periodic audits all software licenses ensure compliance and integrity our software inventory data Regular checks employee software and license counts may conducted random basis The Company will also conduct complete Software and License Audit annually and compare the SDCS. Insert additional descriptions the tasks performed Off site Storage Off site storage all information contained the SDCS shall facilitated the Department This includes whenever possible copies all installation media documentation licenses serial numbers and other relevant information the case where multiple copies the same software are being utilized only necessary store single copy each version off site Data will updated regular basis and more than one member the Incident Response Team shall have access this storage all times. Insert additional descriptions the tasks performed Proof Ownership All original supporting Proof Ownership documents shall retained off site while the Company shall retain copies Proof Ownership onsite for auditing purposes. Insert additional descriptions the tasks performed Documentation Whenever possible photocopies reproductions all documentation should made for employee use while the originals are stored off site. Insert additional descriptions the tasks performed Plan Objectives This Software Disaster Recovery Plan may superseded actions required the Company Disaster Recovery Plan DRP and part the Company Business Continuity Plan BCP The following shall considered objectives the Software Disaster Recovery Plan. Company Recovery Point Objective RPO The Company Recovery Point Objective RPO shall considered point time which data must restored order acceptable Company within the context the following. The difference time between back resource asset and the disruptive event that could occur. The Company tolerance for loss data and continued operations The Company tolerance for risk and exposure risk during disaster event. The Company exposure cost and financial loss due restoration data and time spent recovering entering data. Company Recovery Time Objective RTO The Company Recovery Time Objective RTO shall the acceptable boundary time which recovery efforts must accomplished order meet the expectations the Company has determined critical when disaster event business interruption occurs. individual RTO may established for each process covered under this recovery plan established during the Company Business Impact Analysis BIA for each department RTO may encompass series processes well All RTOs are determined Senior Management and the Executive Team. Implementation the Plan Insert the overall objectives for implementation the plan Your Software Disaster Recovery Plan may contain several different approaches for certain events large small. Definition Software Disaster Event software disaster event shall defined event occurrence that results the sudden unexpected loss key software licenses components dependencies any other failure. event may include but not limited Fire smoke damage Floods water damage Power and utility failures Natural disasters Terrorist attacks Theft criminal activity Computer viruses security breaches Hardware and equipment failures Human error omissions Legal issues Riots strikes and civil disturbances Planned maintenance and testing Unplanned maintenance and testing Notification Event the event occurrence any event disaster regardless known impact single user department the entire company the following people must immediately notified. Insert notification information here including back secondary notification information specific person will noted Disaster Recovery Coordinator you will want specify who your organization must take that role sure specify all back and secondary notifications that must take place well who the role Disaster Recovery Coordinator falls the event that the primary point contact cannot reached. Event Recovery Timelines Within the first Hours hours after notification event the Disaster Recovery Coordinator will take the following steps. Assess all damage Company and its operations including the determination all affected locations and resources Special consideration should made for all dependent systems and software which are not yet impacted event but share dependency with impacted software resource. Consult all relevant Company Recovery Time Objectives RTO and Company Recovery Point Objectives RPO. Notify Senior Management and the proper Executives Notify all support staff responsible for implementing this plan and recovery services including all vendors who have responsibility for implementing the Company Business Continuity Plan BCP. Make decisions regarding containing the damage from the disaster event and decide whether recovery enacted whether back resources must employed. Within the first Hours hours after notification event the Disaster Recovery Coordinator will take the following steps. the disaster event impacts Company customers and after successful contact with Senior Management Executives contact all Customer Support Managers provide them with information concerning service restrictions limitations other downtime that may occur. Notify all disaster recovery vendors services off site storage providers deemed necessary. Schedule all support staff employees with disaster recovery duties and task them with recovery efforts. Schedule obtaining all relevant back data software manuals and other required resources. Contact all Managers Supervisors Department Heads impacted the Disaster Event Within the first Hours hours after notification event the Disaster Recovery Coordinator will take the following steps. Provide Senior Management and the proper Executives with updated assessment recovery progress report and estimate timeline for the recovery schedule. the case critical software and systems not immediately recoverable the Disaster Recovery Coordinator shall have discretion enact emergency funding Insert Disaster Recovery Funding Amount cover the procurement resources. Review all software support contracts and contact all software vendors alert them for emergency assistance temporary license keys enact provisions support agreements that may exist between the vendor and Company. Proceed with acquisition back resources deemed necessary this time Proceed with activation alternate resources sites locations other critical resources Secure all recovery logs Secure alternate base operations deemed necessary Carry out Company wide communication subject Senior Management and Executive approval. Carry out customer communication subject Senior Management and Executive approval Within the first Hours hours after notification event the Disaster Recovery Coordinator will take the following steps. Provide Senior Management and the proper Executives with updated assessment recovery progress report and estimate timeline for the recovery schedule. Begin installation and testing all software and critical applications Begin restoration reloading all critical dependent data Enact monitoring all restored software and operation software verify data integrity and operational continuity. Coordinate with Customer Support Managers and Department Heads confirm successful resumption schedules and functionality restored software and systems. Within Days days after successful restoration from event the Disaster Recovery Coordinator will take the following steps. Provide Senior Management and the proper Executives with updated assessment and recovery progress report noting any outstanding reduction functionality loss data extended estimate timeline for the recovery such items subject each relevant RPO The Disaster Recovery Coordinator will also coordinate evaluation and certification that each objective the Company RPO for impacted business process has been met. Store all recovery logs Provide Senior Management and the proper Executives Disaster Recovery Report DRR. Upon successful restoration all critical software and systems complete new assessment all systems and software associated with relating the recovery. Complete assessment all vendor performance Complete assessment all support staff performance related the recovery and enactment the Software Disaster Recovery Plan. recovery efforts included use off site alternate locations resources vendors work with Senior Management and Executives outline plan for restoration and normalization usage such assets and resources including additional back allowing for back ups for the back ups essence resources deployed. Software Recovery Plan Testing Insert the objectives and requirements for testing ensure that the plan operates correctly within the parameters set forth the Company and the provisions its BCP. Plan Objectives Mandates The objectives set forth RPO and RTO objectives should considered the overall goals the Company disaster event They are not exact mandates Individual department policies and procedures contingency plans and other disaster recovery plans may outline additional instructions followed. Plan Performance Testing Insert the objectives and requirements for testing ensure that the plan operates correctly regard normal operation response and execution times scalability portability and all other performance requirements within the business environment. Plan Regression Testing Insert the objectives and requirements for testing ensure that any changes applied the plan not affect functions previously tested. Plan Acceptance Testing Insert the objectives and requirements for testing ensure that the plan meets all criteria and deliverables set forth the Company Business Continuity Plan BCP The Acceptance Testing important ensure that all requirements are met and that all components modules hardware requirements and recovery and restore operations function and that viable plan exists demonstrate such functionality for customer. Plan Testing Process and Methods Insert the specific testing process and methods used performing each test activity this section you will describe and define each type test that the Software Disaster Recovery Plan contains You may attach additional exhibits this section your testing plan requires them. Test Deliverables Insert the specific deliverables and documents that are delivered from the testing process Test deliverables may include incremental data data derived from incomplete tests Typical test deliverables include but are not limited. Individual RTO RPO Test Summary Reports Group Department RTO RPO Summary Reports Individual and Combined Test Logs Test Metrics and Benchmark Reports Test Incident Reports Testing Task and Requirements List description tasks and the skills required for performing testing part the deliverables. Examples Task Name Insert description here Responsibility for Task Insert description here Resources Required for Task Insert description here Schedule Timeline for Task Insert description here Testing Hardware and Environmental Requirements List description the hardware and environmental requirements for performing testing part the deliverables. Examples Hardware Requirement Name Insert description here Software Requirement Name Insert description here Security Resources Requirement Name Insert description here Specific Tools Requirement Name Insert description here Specific Documentation Requirement Name Insert description here Specific Risks and Assumptions Insert description here Focus restraints such resource availability time constraints staff and developer availability and all other external factors that can influence testing. Risk and Assumption Contingency Plan Insert description the contingency plan for each item listed above Change Request and Management description the Software Disaster Recovery Plan change request and change management procedure Describe the process that must followed for submission review and authorization for all requests for change the Software Disaster Recovery Plan any change any part the deliverables. Approval for Software Disaster Recovery Plan description the personnel authorized approve the Software Disaster Recovery Plan Their names titles and signatures must accompany this document. Approver Title Date signed Approver Title Date signed Approver Title Date signed Approver Title Date signed Appendices description all other supporting information required for the understanding and execution the Software Disaster Recovery Plan and requirements. All Software Disaster Recovery Plan documents require the following two appendices. Definitions Acronyms Abbreviations description the definitions important terms abbreviations and acronyms This may also include Glossary terms. References listing all citations all documents and meetings referenced used the preparation this Software Disaster Recovery Plan. Customer Initials Developer Initials