Earthquake located on the San Andreas Fault line Essay

An quake that registered 7.8 on the Richter Scale which lasted approximately 1 minute ingestd catastrophic defile to the City of Berkeley and LPHG. As a result of the Earthquake 31 employees perished including 1 as a result of the H1Z1 virus which had an emergebreak in the agitate of the catastrophe. The damage and loss of life has caused significant delays to the exclude of LPHGs release of EFHG. DRP Documents (e.g., catastropheretrieval picture, backup programs etc.) Include specific details slightly the accounts, including completeness. The Disaster Preparedness send off was not written as exhaustively as possible and left little direction to the disaster reco really team up. it was missing major discipline, such as a list of circumstantial service, Employee contact information and vendor contact information.see more than digest of san andreas movieThe Business jolt analysis for this type of scenario or both disaster was never completed so there was little inf ormation to help the disaster preparedness team as farther as how this disaster forget impact the shapings operations. The complement Policy was written good and get under ones skind information on the backup schedule and entrepot locations. It in like manner listed the backup methods used and the length of time full backups were kept for. The put down also included instruction manual to restore selective information from both derivative and full backups, but did not address what to do in a disaster scenario such as this. Lastly, the document does not address data storage at an offsite location, which would be beneficial if the whole campus is lost during an taking into custody.Post-Disaster reply SummaryBecause the DRP was not completed straight-lacedly there was not ample information available to employees, and they were not able to respond properly. They had to find employees names and addresses on their own since this information was missing from the DRP. Since n o Business Impact analysis was do for this type of situation there was no pertinent information available to help the DR team members through this specific situation. bingle bright spot is that they placements data has been protected. specialisms of Disaster result EVALUATION fortissimo 1Strength enlargeSummary of StrengthThe attendant scheme was set up and in localize and data was protected and stored in multiple locations to en genuine its safety. excessly, the data retention policy made sure that full backups were kept for a period of at least 2 weeks and that differential backups were used in addition to full backups.Contributing FactorsPlans in that respect was a data backup plan in placePoliciesPolicies were clearly outlined in the assuagement and recovery Policy document, and were macrocosm detectedDocumentsThe Backup and convalescence Policy was able to provide enough corroboration to excuse procedures for backing up data.Positive ConsequencesBecause the Poli cy was in place and was being followed, the Organization was able to retain all of its data through this disaster. once ruler operations resume that data can be restored. ways to ImproveThe locations of data storage should be revised to surrender for an offsite storage location. currently both data storage locations are located on campus. At least one of these locations pauperisations to be changed to an offsite location to allow for greater chance of data retention in case a disaster strikes that wipes out the whole campus.Strength 2Strength lucubrateSummary of Strength data recovery plan was written and procedures were in place to restore data in case of emergency. Since this was prepared the organization can restore operations successfully and resume work when normal operations begin againContributing FactorsPlansData restoration plan was written and in placePoliciesPolicies were clearly defined in Backup and recovery policy document.DocumentsBackup and Recovery document pro vides clear instructions to follow in case of emergency and outlines standard by step exploit to restore dataPositive ConsequencesSince the Backup and recovery document was in place and provided clear instructions this allows for a quicker recovery time to restore data once normal operations resume.ship canal to ImproveThe Data recovery document should be refined to include the priority of data restoration when all course functions have been compromisedStrength 3Strength DetailsSummary of StrengthDisaster Recovery team had previously prepared Disaster preparedness plan, a Backup and Recovery Policy, and a Business Impact Assessment. Contributing FactorsPlansHaving these plans in place gift the Disaster Recovery team the instructions they need when disaster strikesPolicies on that point were policies in place for the Disaster Recovery team to follow these documentsDocumentsDocuments were readily available and helped provide basic guidance to Disaster recovery Team Positive Conseq uencesHaving the authentication available helped the Disaster Recovery team kick off the process to restore the organization to operable stance. ways to ImproveThese documents need to be thoroughly come offed after the organization is restored to operational status. When they are reviewed they need to be more thoroughly filled out and include any lessons learned from the current disaster.Areas for amelioration of Disaster Response EVALUATIONArea for Improvement 1Area for Improvement DetailsSummary of Area for ImprovementDocumentation call for to be alter and completed. The Documentation that existed, though helpful did not provide any nationwide guidance to the disaster recovery team.Contributing FactorsPlansThe Disaster Preparedness plan and the Business Impact analysis were not completed properly.PoliciesPolicies for developing proper disaster recovery documentation were not in place and as a result the documentation to support it was not correctly done DocumentsDisaster r ecovery documentation was not complete and did not give employees enough information to used during the disaster recovery process ConsequencesThere are multiple scenarios that can be created from the lack of preparedness. At the very least the lack of documentation and foresight into planning can cause a delay in the recovery process for the organization. On the more extreme side this can put the organization out of business because the organization can take an extraordinary amount of time to shine to normal operating conditionsWays to ImproveReview existing documentation and ensure that is it done completely. This is an incredibly important and clearly necessary approach. Additional documentation will have to be created in order to aid the Emergency Response team in the future.Area for Improvement 2Area for Improvement DetailsSummary of Area for ImprovementData storage and Business Continuity plan did not identify the need for an off campus site to store data backups and allow fo r restoration of ITservices in case of emergency Contributing FactorsPlansA plan needs to be developed that involves identifying an off campus site in case of emergencyPoliciesPolicies will need to be created to identify when an alternate site is involve to be used and how to go about restoring services from that site. DocumentsDocumentation will have to be written to support proper procedure for legal transfer alternate site up during emergency situations.ConsequencesWithout an off campus secondary site, the organization runs the risk of total destruction should an emergency happen that destroys or compromises the primary(prenominal) campus.Ways to ImproveA secondary site with proper equipment that is far enough away from main campus could enable the organization to continue operations even if the main campus is compromised.Area for Improvement 3Area for Improvement DetailsSummary of Area for ImprovementThere is no process in place to validate and review the various documents fo r the Disaster Recovery Plan. Additionally no Disaster response teams have been identified to review and execute these plans when needed.Contributing FactorsPlans every Disaster Recovery documentation should be completed and review periodically. A process to validate and test the plan should be put into place. PoliciesPolicies and procedures should be created to ensure that documentation is completed and reviewedDocumentsAll documents involving Disaster Recovery need to updated and reviewed on a regular basis.ConsequencesSince the documentation was done so haphazardly, the ability to return to normal operation status in a timely manner is put in jeopardy. tear down worse,this can cause the organization to cease to exist.Ways to Improve construct a Disaster Recovery team and put them in constitute of documenting and planning all facets of disaster recovery. Have them update and add the infallible documentation and have disaster recovery drills to verify the plans. Additionally, th e team should take their findings from testing and continually update and try to improve the policy.