Introduction to Business Continuity Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. Section 3 : Business Continuity Introduction to Business Continuity Chapter 11

Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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

What is Business Continuity Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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”

What is Information Availability (IA) Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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

Causes of Information Unavailability Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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

Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. Impact of Downtime Lost Revenue Know the downtime costs (per hour, day, two days...) Number of employees impacted (x hours out * hourly rate) Damaged Reputation Customers Suppliers Financial markets Banks Business partners Financial Performance 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... Direct loss Compensatory payments Lost future revenue Billing losses Investment losses Lost Productivity

Measuring Information Availability Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. Measuring Information Availability MTTR – Time to repair or ‘downtime’ Response Time Recovery Time Detection Repair Restoration Time Incident Diagnosis Recovery Incident Detection elapsed time MTBF – Time between failures or ‘uptime’ Repair time 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)

Availability Measurement – Levels of ‘9s’ Availability Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. Availability Measurement – Levels of ‘9s’ Availability % Uptime % Downtime Downtime per Year Downtime per Week 98% 2% 7.3 days 3hrs 22 min 99% 1% 3.65 days 1 hr 41 min 99.8% 0.2% 17 hrs 31 min 20 min 10 sec 99.9% 0.1% 8 hrs 45 min 10 min 5 sec 99.99% 0.01% 52.5 min 1 min 99.999% 0.001% 5.25 min 6 sec 99.9999% 0.0001% 31.5 sec 0.6 sec

Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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

BC Terminologies (Cont.) Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. BC Terminologies (Cont.) 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 Seconds Minutes Hours Days Weeks Tape Backup Periodic Replication Asynchronous Replication Synchronous Replication Tape Restore Disk Restore Manual Migration Global Cluster Recovery-point objective Recovery-time objective

Business Continuity Planning (BCP) Process Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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

Business Continuity (BC) Planning Lifecycle Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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

Business Continuity (BC) Planning Lifecycle Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. Business Continuity (BC) Planning Lifecycle Figure. BC planning lifecycle

Establishing objectives Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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.

Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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.

Designing and developing Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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.

Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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.

Training, testing, assessing, and maintaining Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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.

BC Technology Solutions Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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

Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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

Multi-pathing Software Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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

Backup and Replication Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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

Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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

Concept in Practice – EMC PowerPath Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. 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 PowerPath SCSI Driver SCSI Driver SCSI Driver SCSI Driver SCSI Driver SCSI Driver SERVER SCSI Controller Storage Network LUN LUN STORAGE LUN LUN

Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved.  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?

Copyright © 2009 EMC Corporation. Do not Copy - All Rights Reserved. #1 IT company For more information visit http://education.EMC.com