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 outbreak in the wake of the catastrophe. The damage and loss of life has caused significant delays to the release of LPHG’s release of EFHG. DRP Documents: (e.g., disaster recovery plan, backup plans etc.) Include specific details about the documents, including completeness. The Disaster Preparedness plan was not written as thoroughly as possible and left little direction to the disaster recovery team. it was missing major information, such as a list of critical services, Employee contact information and vendor contact information.
The Business Impact analysis for this type of scenario or any disaster was never completed so there was little information to help the disaster preparedness team as far as how this disaster will impact the organizations operations. The Backup 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 full backups were kept for. The document also included instructions to restore data from both differential 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 emergency.
The Business plan on Data Warehouse Information Database Analysis
1. DATA MINING 1. 1 INTRODUCTION TO DATA MINING The past two decades has seen a dramatic increase in the amount of information or data being stored in electronic format. This accumulation of data has taken place at an explosive rate. It has been estimated that the amount of information in the world doubles every 20 months and the size and number of databases are increasing even faster. The ...
Post-Disaster Response Summary:
Because the DRP was not completed properly there was not enough 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 no Business 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.
Strengths of Disaster Response EVALUATION
Strength #1:
Strength Details:
Summary of Strength:
The backup plan was set up and in place and data was protected and stored in multiple locations to ensure its safety. Additionally, 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 Factors:
Plans
There was a data backup plan in place
Policies
Policies were clearly outlined in the Backup and Recovery Policy document, and were being followed
Documents
The Backup and Recovery Policy was able to provide enough documentation to explain procedures for backing up data.
Positive Consequences:
Because the Policy was in place and was being followed, the Organization was able to retain all of its data through this disaster. once normal operations resume that data can be restored.
Ways to Improve:
The 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.
The Research paper on Data Collection 3
In the hospitality business, employee retention and low turnover is of utmost importance. Employees are the foundation of any successful operation. Employees provide direct communication with customers, support organizational initiatives, boost profit, curb losses, and build future success. Denihan is a hospitality company that began in 1903 as a dry cleaning company by Benjamin J. Denihan, an ...
Strength #2:
Strength Details:
Summary 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 again
Contributing Factors:
Plans
Data restoration plan was written and in place
Policies
Policies were clearly defined in Backup and recovery policy document.
Documents
Backup and Recovery document provides clear instructions to follow in case of emergency and outlines step by step process to restore data
Positive Consequences:
Since 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 Improve:
The Data recovery document should be refined to include the priority of data restoration when all business functions have been compromised
Strength #3:
Strength Details:
Summary of Strength:
Disaster Recovery team had previously prepared Disaster preparedness plan, a Backup and Recovery Policy, and a Business Impact Assessment. Contributing Factors:
Plans
Having these plans in place give the Disaster Recovery team the instructions they need when disaster strikes
Policies
There were policies in place for the Disaster Recovery team to follow these documents
Documents
Documents were readily available and helped provide basic guidance to Disaster recovery Team Positive Consequences:
Having the documentation available helped the Disaster Recovery team kick off the process to restore the organization to operational status. Ways to Improve:
These 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 EVALUATION
Area for Improvement #1:
Area for Improvement Details:
Summary of Area for Improvement:
The Essay on Project: Document Retention Policy and Litigation Hold Notices
Purpose The purpose of this project is to provide you with an opportunity to create a document retention policy. You will also learn how to serve a litigation hold notice for an educational institute. The following aspects of litigation and document retention are covered: Applicability of availability, integrity, and confidentiality (AIC) concepts Confidentiality of personal information and ...
Documentation needs to be improved and completed. The Documentation that existed, though helpful did not provide any comprehensive guidance to the disaster recovery team.
Contributing Factors:
Plans
The Disaster Preparedness plan and the Business Impact analysis were not completed properly.
Policies
Policies for developing proper disaster recovery documentation were not in place and as a result the documentation to support it was not correctly done Documents
Disaster recovery documentation was not complete and did not give employees enough information to used during the disaster recovery process Consequences:
There 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 return to normal operating conditions
Ways to Improve:
Review 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 Emergency Response team in the future.
Area for Improvement #2:
Area for Improvement Details:
Summary of Area for Improvement:
Data storage and Business Continuity plan did not identify the need for an off campus site to store data backups and allow for restoration of IT
services in case of emergency Contributing Factors:
Plans
A plan needs to be developed that involves identifying an off campus site in case of emergency
Policies
Policies 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. Documents
Documentation will have to be written to support proper procedure for bringing alternate site up during emergency situations.
Consequences:
Without an off campus secondary site, the organization runs the risk of total destruction should an emergency happen that destroys or compromises the main campus.
The Term Paper on DIRT BIKES USA CO. ACHIEVING OPERATIONAL EXCELLENCE: DEVELOPING A DISASTER RECOVERY PLAN
These days, most companies are having trouble by undesired threat. There are several types of threat that might cost a company being inefficient in total production, thus affect total revenue in the future. The threat might come as a Web Browses, Databases, Viruses, spyware and natural disasters. This section will go over the threats that potentially disrupt the continue operation of Dirt bikes. ...
Ways to Improve:
A 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 #3:
Area for Improvement Details:
Summary of Area for Improvement:
There 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 Factors:
Plans
All Disaster Recovery documentation should be completed and review periodically. A process to validate and test the plan should be put into place. Policies
Policies and procedures should be created to ensure that documentation is completed and reviewed
Documents
All documents involving Disaster Recovery need to updated and reviewed on a regular basis.
Consequences:
Since 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 Improve:
Create 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.
