1 / 18

Introduction to Business Continuity

Introduction to Business Continuity. Module 3.1. Introduction to Business Continuity. After completing this module, you will be able to: Define Business Continuity and Information Availability Detail impact of information unavailability Define BC measurement and terminologies

dyllis
Download Presentation

Introduction to Business Continuity

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Introduction to Business Continuity Module 3.1

  2. Introduction to Business Continuity After completing this module, you will be able to: • Define Business Continuity and Information Availability • Detail impact of information unavailability • Define BC measurement and terminologies • Describe BC planning process • Detail BC technology solutions Introduction to Business Continuity

  3. What is Business Continuity • Business Continuity is preparing for, responding to, and recovering from an application outage that adversely affects business operations • Business Continuity solutions address unavailability and degraded application performance • BC is an integrated and enterprise wide process and set of activities to ensure “information availability” Introduction to Business Continuity

  4. What is Information Availability (IA) • IA refers to the ability of an infrastructure to function according to business expectations during its specified time of operation • IA can be defined in terms of three parameters: • Accessibility • Information should be accessible at right place and to the right user • Reliability • Information should be reliable and correct • Timeliness • Information must be available whenever required Introduction to Business Continuity

  5. Causes of Information Unavailability Disaster (<1% of Occurrences) Natural or man made Flood, fire, earthquake Contaminated building Unplanned Outages (20%) Failure Database corruption Component failure Human error Planned Outages (80%) Competing workloads Backup, reporting Data warehouse extracts Application and data restore Introduction to Business Continuity

  6. Lost Productivity Lost Revenue Know the downtime costs (per hour, day, two days...) • Number of employees impacted (x hours out * hourly rate) • Direct loss • Compensatory payments • Lost future revenue • Billing losses • Investment losses Damaged Reputation Financial Performance • Customers • Suppliers • Financial markets • Banks • Business partners • Revenue recognition • Cash flow • Lost discounts (A/P) • Payment guarantees • Credit rating • Stock price Other Expenses Temporary employees, equipment rental, overtime costs, extra shipping costs, travel expenses... Impact of Downtime Introduction to Business Continuity

  7. Measuring Information Availability MTTR – Time to repair or ‘downtime’ Response Time Recovery Time Detection Repair Restoration Time Incident Diagnosis Recovery Incident • MTBF:Average time available for a system or component to perform its normal operations between failures • MTTR:Average time required to repair a failed component IA = MTBF / (MTBF + MTTR) or IA = uptime / (uptime + downtime) MTBF – Time between failures or ‘uptime’ Detection elapsed time Repair time Introduction to Business Continuity

  8. Availability Measurement – Levels of ‘9s’ Availability Introduction to Business Continuity

  9. BC Terminologies • Disaster recovery • Coordinated process of restoring systems, data, and infrastructure required to support ongoing business operations in the event of a disaster • Restoring previous copy of data and applying logs to that copy to bring it to a known point of consistency • Generally implies use of backup technology • Disaster restart • Process of restarting from disaster using mirrored consistent copies of data and applications • Generally implies use of replication technologies Introduction to Business Continuity

  10. Recovery Point Objective (RPO) Point in time to which systems and data must be recovered after an outage Amount of data loss that a business can endure Recovery Time Objective (RTO) Time within which systems, applications, or functions must be recovered after an outage Amount of downtime that a business can endure and survive Weeks Weeks Tape Backup Tape Restore Days Days Periodic Replication Disk Restore Hours Hours Asynchronous Replication Manual Migration Minutes Minutes Synchronous Replication Global Cluster Seconds Seconds BC Terminologies (Cont.) Recovery-point objective Recovery-time objective Introduction to Business Continuity

  11. Business Continuity Planning (BCP) Process • Identifying the critical business functions • Collecting data on various business processes within those functions • Business Impact Analysis (BIA) • Risk Analysis • Assessing, prioritizing, mitigating, and managing risk • Designing and developing contingency plans and disaster recovery plan (DR Plan) • Testing, training and maintenance Introduction to Business Continuity

  12. BC Technology Solutions • Following are the solutions and supporting technologies that enable business continuity and uninterrupted data availability: • Single point of failure • Multi-pathing software • Backup and replication • Backup recovery • Local replication • Remote replication Introduction to Business Continuity

  13. Resolving Single Points of Failure Clustered Servers Redundant Arrays Heartbeat Connection Redundant Ports Client FC Switches IP Storage Array Storage Array Remote Site Redundant Network Redundant Paths Redundant FC Switches Introduction to Business Continuity

  14. Multi-pathing Software • Configuration of multiple paths increases data availability • Even with multiple paths, if a path fails I/O will not reroute unless system recognizes that it has an alternate path • Multi-pathing software helps to recognize and utilizes alternate I/O path to data • Multi-pathing software also provide the load balancing • Load balancing improves I/O performance and data path utilization Introduction to Business Continuity

  15. Backup and Replication • Local Replication • Data from the production devices is copied to replica devices within the same array • The replicas can then be used for restore operations in the event of data corruption or other events • Remote Replication • Data from the production devices is copied to replica devices on a remote array • In the event of a failure, applications can continue to run from the target device • Backup/Restore • Backup to tape has been a predominant method to ensure business continuity • Frequency of backup is depend on RPO/RTO requirements Introduction to Business Continuity

  16. Module Summary Key points covered in this module: • Importance of Business Continuity • Types of outages and their impact to businesses • Information availability measurements • Definitions of disaster recovery and restart, RPO and RTO • Business Continuity technology solutions overview Introduction to Business Continuity

  17. PowerPath Storage Network SCSIController SCSIController SCSIController SCSIController SCSIController SCSIController LUN LUN LUN LUN Concept in Practice – EMC PowerPath Host Application (s) • Host Based Software • Resides between application and SCSI device driver • Provides Intelligent I/O path management • Transparent to the application • Automatic detection and recovery from host-to-array path failures SCSI Driver SCSI Driver SCSI Driver SCSI Driver SCSI Driver SCSI Driver SERVER STORAGE Introduction to Business Continuity

  18. Check Your Knowledge • Which concerns do business continuity solutions address? • “Availability is expressed in terms of 9s.” Explain the relevance of the use of 9s for availability, using examples. • What is the difference between RPO and RTO? • What is the difference between Disaster Recovery and Disaster Restart? • Provide examples of planned and unplanned downtime in the context of data center operations. • What are some of the Single Points of Failure in a typical data center environment? Introduction to Business Continuity

More Related