Introduction to Business Continuity

1. Section 3 : Business Continuity Introduction to Business Continuity Chapter 11

2. Chapter Objective After completing this chapter, 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

3. What is Business Continuity (BC) • 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 • Business Continuity is an integrated and enterprise wide process and set of activities to ensure “information availability”

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: • Reliability • The components delivering the information should be able to function without failure, under stated conditions, for a specified amount of time • Accessibility • Information should be accessible at the right place and to the right user • Timeliness • Information must be available whenever required

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

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

7. Impact of Downtime • Average cost of downtime per hour = average productivity loss per hour + average revenue loss per hour • Where: • Productivity loss per hour = (total salaries and benefits of all employees per week) / (average number of working hours per week) • Average revenue loss per hour = (total revenue of an organization per week) / (average number of hours per week that an organizations is open for business)

8. 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

9. Availability Measurement – Levels of ‘9s’ Availability

10. 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

11. 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

12. 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

13. Business Continuity (BC) Planning Lifecycle BC planning must follow a disciplined approach like any other planning process. Organizations today dedicate specialized resources to develop and maintain BC plans. From the conceptualization to the realization of the BC plan, a lifecycle of activities can be defined for the BC process. The BC planning lifecycle includes five stages: 1. Establishing objectives 2. Analyzing 3. Designing and developing 4. Implementing 5. Training, testing, assessing, and maintaining

14. Business Continuity (BC) Planning Lifecycle Figure. BC planning lifecycle

15. Establishing objectives • Determine BC requirements. • Estimate the scope and budget to achieve requirements. • Select a BC team by considering subject matter experts from all areas of the business, whether internal or external. • Create BC policies.

16. Analyzing • Collect information on data profiles, business processes, infrastructure support, dependencies, and frequency of using business infrastructure. • Identify critical business needs and assign recovery priorities. • Create a risk analysis for critical areas and mitigation strategies. • Conduct a Business Impact Analysis (BIA). • Create a cost and benefit analysis based on the consequences of data unavailability. • Evaluate options.

17. Designing and developing • Define the team structure and assign individual roles and responsibilities. For example, different teams are formed for activities such as emergency response, damage assessment, and infrastructure and application recovery. • Design data protection strategies and develop infrastructure. • Develop contingency scenarios. • Develop emergency response procedures. • Detail recovery and restart procedures.

18. Implementing • Implement risk management and mitigation procedures that include backup, replication, and management of resources. • Prepare the disaster recovery sites that can be utilized if a disaster affects the primary data center. • Implement redundancy for every resource in a data center to avoid single points of failure.

19. Training, testing, assessing, and maintaining • Train the employees who are responsible for backup and replication of business-critical data on a regular basis or whenever there is a modification in the BC plan. • Train employees on emergency response procedures when disasters are declared. • Train the recovery team on recovery procedures based on contingency scenarios. • Perform damage assessment processes and review recovery plans. • Test the BC plan regularly to evaluate its performance and identify its limitations. • Assess the performance reports and identify limitations. • Update the BC plans and recovery/restart procedures to reflect regular changes within the data center.

20. BC Technology Solutions • The following are the solutions and supporting technologies that enable business continuity and uninterrupted data availability: • Fault tolerant configuration • To avoid single-point of failure • Multi-pathing software • Backup and replication • Backup recovery • Local replication • Remote replication

21. Implementation of Fault Tolerance 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

22. 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

23. 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

24. Chapter Summary Key points covered in this chapter: • 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

25.  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 storage infrastructure operations. • What are some of the Single Points of Failure in a typical data center environment?

26. #1 IT company For more information visit http://education.EMC.com