Hurricane Preparedness and Disaster Recovery


Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Hurricane Preparedness and Disaster Recovery

  1. 1.  Step 1 – Send flowers. Step 2 – Invoke the DETAILED plan that you already had in place to ensure continuance after the situation. Step 3 – Business as usual!
  2. 2.  If you DIDN’T have a Disaster Recovery Plan in place…  Accept the fact that you’re going to lose time, money, reputation and clients.
  3. 3.  FACTS about lack of Disaster Recovery Planning Understanding the impact to your business TYPES of Disaster STEPS to Protect your business Questions
  4. 4.  40% of the companies were out of business within 6 week 40% of enterprises that experience any disaster go out of business within five years (Gartner)
  5. 5. 10 years ago it cost the average company$100,000- $1,000,000/year for desktop orienteddisasters. This cost continues to growexponentially!
  6. 6.  Your safety net for: Power failure Virus, hacking, internal Underground cable cuts or external or failures Fire, flood, hurricanes, Mistakes in system and other natural administration disasters
  7. 7. Our Solutions:  Backup  Restore  Replace  Direct Employees to new location
  8. 8.  A plan to restore ALL of these components must be in place. The system must be able to put them back together if your business is to survive a disaster.
  9. 9.  DR focusing only on the technical components. Consider:  Lost productivity and idle employees  Missed service level agreements  Diminished reputation for customer service  Increased technical support costs for onsite repair  Loss of customer confidence  Legal Liabilities  Regulatory Fines  Downward stock prices  …and more…
  10. 10.  BCP addresses:  Risk of lost revenue and productivity  Plan of action for continuing the business, NOT computers.
  11. 11.  Example of items that typical planning might leave out: Sources and Business Consumer’s processes Data Roles & Left Out Reconstitution Responsibilities Items What happens at the absence of Documented Key Individuals Procedures Order of Recovery
  12. 12.  Rarely documented Typically defined only in the combined knowledge of key employees (this is true of the “big picture” as well as details of each departmental process) One of the most difficult things to put back if key employees are not available.
  13. 13. ExceptionMaking decisionto invoke plan Handling The Second in Signature Decision of Charge Authority Priorities Being responsible for each element of plan
  14. 14.  Absence of key individuals  A more difficult thing to consider  Mental notes  Revenge (sabotage or withholding information)
  15. 15.  Sources and Consumers of Information.  Detailed data flow  Detailed process flow  Updated documentation
  16. 16.  Set expectations up front. Help to design budgets. Assign priorities for recovery.
  17. 17.  Create documentation so that a contractor can start your business Create policies and procedures for updating
  18. 18.  When is a disaster over? How to go back to business as usual? What steps need to be taken?
  19. 19. Now lets talk about the things that typical planning “almost always” leaves out:  Mental notes  Periodic testing  Updating procedures and plan content  Moving DR Planning to the DR site  Details, Details, Details!!!
  20. 20.  32% of all data lost is due to human error.
  21. 21.  Moving Planning to the DR Site A method is needed that will:  Bring knowledge together  Document it  Enable processes to be reconstructed (possibly without the help of key employees)  Enforce periodic testing and updating of the plan.
  22. 22. Continuance Planning Defines and Documents: Assistance with Testing & Department Updating Processes Source of Documentation Data Consumers of Relationships Data Cost Budget Ramifications Justification Recovery Solution Criteria Design
  23. 23. Planning is approached in phases: Process Analysis• Data Flows Risk Analysis• Cost/Effective Disaster Recovery• Traditional Technical Component Implementation and Testing• Annual or After Significant Changes
  24. 24. By Unit Continuance Planning can To In PracticalPhases be Extents Implemented: As Single Phase
  25. 25.  QUESTIONS?  Jeffrey Robles ▪ ▪ ▪ Work: (305) 592 – 5433 ▪ Cell: (305) 562 – 3775
  26. 26. Thank You!