Task 3 After Action Report

A Disaster Recovery Plan (DRP) focuses on the recovery of IT systems, applications, and data in the

2. Disaster recovery: A great disaster recovery plan will be added to the SLA. We will have a team in place with 24 hours support if the system is compromised. We will promise to have systems back up in running in 36 hours. Data will be back

The Data recovery document should be refined to include the priority of data restoration when all business functions have been compromised

PER REPORTER: Jamita said she use to represent Ayanna in the past through the youth court for delinquent matters. Jamita said this morning she received a call from Shavon Sykes a counselor at Warren Yazoo Mental Health regarding Ayanna. Jamita said Shavon told her, she saw her client referring to Ayanna on the corner of Washington and Lee Street surrounded by police. Jamita said she then left her office to go and check on the child because she knew she had been having some issues at home. Jamita said when she arrived to the scene she noticed Ayanna had clothes in her bag and was planning to run away. Jamita said she asked Ayanna why she was running away from home and she expressed no longer wanting to be at home with her mother. Jamita said

This recovery plan can be cloud-based or an external hard drive. If information is stored on another location it would still have to be safe, secure, and HIPPA compliant. Both options have pros and cons, however the database needs to be backed up constantly. If the center was to choose an additional cloud-based system, it should be ready to go if a system outage occurs. The center could possibly have backed up data on another workstation site

Let 's go back to daily backups for an example. If you back up at night at 6:00 p.m. and the server goes down the following day at 4:00 p.m., then you 've potentially lost 22 hours of data that was created during that day. If you have no ability to recreate that data, then the data is lost.

The damages were catastrophic as houses lay in ruin and debris littered the roads. There were mudslides and fallen rocks that paved the roads and made them impassible for vehicles to get through. Ultimately by the roads being clogged up the response time by rescue workers and essential personal were hampered. This also made it exceptionally difficult for supplies to be rushed to the locations for the earthquake survivors. As some were digging and excavating for survivors they were being halted by aftershocks and falling debris from above. Approximately 8000 people were killed either by their houses caving in or by the other disasters this earthquake triggered. It was a real life tragedy that

Because Aircraft Solutions has valuable intellectual property, the cost of data loss can be astronomical. In fact, 17 percent of data loss incidents cannot be retrieved. It is worth noting that the value of the lost data varies widely depending on the incident and, most critically, on the amount of data lost. Should AS experience a data loss, it may take hundreds of man-hours over several weeks to recover and reconstruct. Such prolonged effort could cost a company thousands, even potentially millions, of dollars. Although it is difficult to precisely measure the intrinsic value of data, and the value of different types of data varies, several sources in the computer literature suggest that the value of 100 megabytes of data is valued at approximately $1 million, translating to $10,000 for each MB of lost data (Smith, 2003). The National Archives and Records report that 93% of companies that lost their data center for 10 days or more due to a disaster filed for bankruptcy within one year of the disaster. 50% of businesses that found themselves without data management

The earthquake lasted a total of 45 seconds, but 26 aftershocks occurred over an extended amount of time afterwards. When the earthquake hit, most people, other than some police officers, were asleep. The earthquake had a magnitude of 7.9 on the richter scale, so the not so earthquake proof buildings, fell on people as they woke up. 400,000 people in San Francisco underwent this terrible shaking. There were reports of people feeling the shake from southern Oregon to Los Angeles and inland to Central Nevada. Although, there were rich people that had their houses in places such as Nob Hill. Nob Hill was made completely upon bedrock, making the earthquake quite small and unproblematic. The reason the city had the earthquake so bad, was because the city wasn’t built on bedrock, but built on some dirt and such. During San Francisco’s gold rush, they decided to expand the city, by literally creating their own land, by packing a combination of trash, dirt and sand, and then building over it. They were not anticipating what an earthquake could do to that particular land. That land, also called South of Market, was hit so badly, some buildings sunk in the loose sand, dirt and trash, up to three stories. During the fires, the water mains in the city broke due to the earthquake's intensity. The water was leaked into the soil, creating mud. One building that was over the broken water mains, sunk into the wet mud 3 stories, and the last

In order for a disaster plan to be effectively created, there must be leadership in place. This leadership is in charge of supervising and making local decisions regarding the disaster. Decisions which must be in the best interest of the entire community in attempts to restore the community as quickly as possible after a disaster.

Disaster recovery is the process of an organisation uses to recover access the data, and also hardware that are needed to recollect the performance to be in normal position after a disaster occurs. While disaster recovery plans have to be focus in every aspect in any organisation and bringing the gap closure after destruction it can be like data, hardware, or software have been lost and the manpower that composes much of any organisation.

Disaster Recovery Planning is the critical factor that can prevent headaches or nightmares experienced by an organization in times of disaster. Having a disaster recovery plan marks the difference between organizations that can successfully manage crises with minimal cost, effort and with maximum speed, and those organizations that cannot. By having back-up plans, not only for equipment and network recovery, but also detailed disaster recovery plans that precisely outline what steps each person involved in recovery efforts should undertake, an organization can improve their recovery time and minimize the disrupted time for their normal business functions. Thus it is essential that disaster recovery plans are carefully laid

Valuable assets, including network connectivity, stored data, processes and procedures, and client information can survive centralized disruption or destruction and can be revived quickly through the agency’s

A large US public power provider, with millions of residential and business customers, needed to rethink its disaster recovery program. Due to budget constraints, the utility’s data recovery program had not been updated or tested for several years. Under the existing program, systems recovery could take up to 20 days—an unacceptable timeframe for a

It was noted that with the aid of an external consultant, Bank Solutions had their current data center DRBC Plan written down in the year 2007 and was last tested in the same year. The testing was a shallow table-top walkthrough with no intensive assessments to ensure dependability and compliance to industry standard security frameworks. The plan has taken long before being updated hence some elements of the plan may not be addressed wholly as purposed. With an acute increment and unprecedented growth in information technology and security systems over the years, the outdated DRBCP would prove ineffective at the face of an information security breach or a disaster. This is due to the use of outdated elements such as outdated hardware and software.