Earthquake located on the San Andreas Fault line Essay

An Earthquake that registered 7.8 on the Richter Scale which lasted approximately 1 minute caused catastrophic damage 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 awaybreak in the wake of the catastrophe. The damage and loss of life has caused significant delays to the tucker out of LPHGs release of EFHG. DRP Documents (e.g., casualtyrecovery plan, backup plans etc.) Include specific details about the scrolls, including completeness. The calamity Preparedness plan was not written as thoroughly as possible and left little direction to the disaster recovery team. it was missing major entropy, such as a list of critical services, Employee contact information and vendor contact information.see moresummary of san andreas movieThe line of merchandise bear upon analysis for this type of scenario or any disaster was never finished so there was little information to help the disaster prepa redness team as far as how this disaster will impact the formations operations. The concomitant Policy was written thoroughly and included information on the backup schedule and storage locations. It also listed the backup methods used and the length of time in effect(p) backups were kept for. The document also included instructions to restore data from both differential and full-of-the-moon backups, but did not add onress 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 full-page campus is lost during an requisite.Post- incident repartee SummaryBecause the DRP was not completed strait-lacedly there was not enough information on hand(predicate) 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 no demarcation Impact analysis was done for this type of situation there was no relevant information available to help the DR team members through this specific situation. One bright spot is that they organizations data has been protected. facultys of Disaster reply EVALUATIONStrength 1Strength expoundSummary of StrengthThe Backup plan was set up and in place and data was protected and stored in multiple locations to ensure its safety. Additionally, the data holding policy made sure that full backups were kept for a period of at to the lowest degree 2 weeks and that differential backups were used in addition to full backups. impart FactorsPlansThere was a data backup plan in placePoliciesPolicies were advancely outlined in the Backup and Recovery Policy document, and were world followedDocumentsThe Backup and Recovery Policy was able to provide enough credentials to explain procedures for backing up data.Positive ConsequencesBecause the Policy was in place and was world followed, the Organization was able to retain all of its d ata through this disaster. once normal operations resume that data can be restored. ways to purifyThe locations of data storage should be revised to allow for an offsite storage location. currently both data storage locations are located on campus. At least one of these locations needs 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 DetailsSummary of Strength entropy 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 provides clear instructions to follow in case of emergency and outlines step by step process to restore dat aPositive 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.Ways to repairThe Data recovery document should be refined to include the priority of data restoration when all business 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 give the Disaster Recovery team the instructions they need when disaster strikesPoliciesThere 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 ConsequencesHaving the living available helped the Disaster Recovery team kick off the process to restore the organization to oper ational status. Ways to ImproveThese documents need to be thoroughly reviewed 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 Improvement of Disaster Response EVALUATIONArea for Improvement 1Area for Improvement DetailsSummary of Area for Improvement keep needs to be improved and completed. The Documentation that existed, though helpful did not provide any comprehensive 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 recovery documentation was not complete and did not give employees enough information to used during the disaster recovery process ConsequencesThe re are multiple scenarios that can be created from the lack of preparedness. At the very least the lack of documentation and foresight into cookery 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 swallow 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 assist the requirement Response team in the future.Area for Improvement 2Area for Improvement DetailsSummary of Area for ImprovementData storage and Business Continuity plan did not put the need for an off campus site to store data backups and allow for 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 needed to be used and how to go about restoring services from that site. DocumentsDocumentation will have to be written to support proper procedure for bringing 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 main 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 for the Disaster Recovery Plan. Additionally no Disaster response teams have been identified to review and execute these plans when needed.Contributing FactorsPlansAll Di saster 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. Even worse,this can cause the organization to cease to exist.Ways to ImproveCreate a Disaster Recovery team and put them in charge of documenting and planning all facets of disaster recovery. Have them update and add the required documentation and have disaster recovery drills to verify the plans. Additionally, the team should take their findings from testing and continually update and try to improve the policy.