© 2009 EMC Corporation. All rights reserved. EMC Proven Professional The #1 Certification Program in the information storage and management industry Introduction to Business Continuity Chapter 11 Section 3 : Business Continuity

© 2009 EMC Corporation. All rights reserved. Chapter Objective After completing this chapter, you will be able to: oDefine Business Continuity and Information Availability oDetail impact of information unavailability oDefine BC measurement and terminologies oDescribe BC planning process oDetail BC technology solutions

© 2009 EMC Corporation. All rights reserved. What is Business Continuity (BC) oBusiness Continuity is preparing for, responding to, and recovering from an application outage that adversely affects business operations oBusiness Continuity solutions address unavailability and degraded application performance oBusiness Continuity is an integrated and enterprise wide process and set of activities to ensure “information availability”

© 2009 EMC Corporation. All rights reserved. What is Information Availability (IA) oIA refers to the ability of an infrastructure to function according to business expectations during its specified time of operation oIA can be defined in terms of three parameters: oReliability oThe components delivering the information should be able to function without failure, under stated conditions, for a specified amount of time oAccessibility oInformation should be accessible at the right place and to the right user oTimeliness oInformation must be available whenever required

© 2009 EMC Corporation. 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

© 2009 EMC Corporation. 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

© 2009 EMC Corporation. All rights reserved. Impact of Downtime oAverage cost of downtime per hour = average productivity loss per hour + average revenue loss per hour oWhere: oProductivity loss per hour = (total salaries and benefits of all employees per week) / (average number of working hours per week) oAverage revenue loss per hour = (total revenue of an organization per week) / (average number of hours per week that an organizations is open for business)

© 2009 EMC Corporation. All rights reserved. Measuring Information Availability oMTBF: Average time available for a system or component to perform its normal operations between failures oMTTR: Average time required to repair a failed component IA = MTBF / (MTBF + MTTR) or IA = uptime / (uptime + downtime) Detection Incident Time Detection elapsed time Diagnosis Response Time Repair Recovery Repair time Restoration Recovery Time MTTR – Time to repair or ‘downtime’ Incident MTBF – Time between failures or ‘uptime’

© 2009 EMC Corporation. All rights reserved. Availability Measurement – Levels of ‘9s’ Availability % Uptime% DowntimeDowntime per YearDowntime per Week 98%2%7.3 days3hrs 22 min 99%1%3.65 days1 hr 41 min 99.8%0.2%17 hrs 31 min20 min 10 sec 99.9%0.1%8 hrs 45 min10 min 5 sec 99.99%0.01%52.5 min1 min %0.001%5.25 min6 sec %0.0001%31.5 sec0.6 sec

© 2009 EMC Corporation. All rights reserved. BC Terminologies oDisaster recovery oCoordinated process of restoring systems, data, and infrastructure required to support ongoing business operations in the event of a disaster oRestoring previous copy of data and applying logs to that copy to bring it to a known point of consistency oGenerally implies use of backup technology oDisaster restart oProcess of restarting from disaster using mirrored consistent copies of data and applications oGenerally implies use of replication technologies

© 2009 EMC Corporation. All rights reserved. BC Terminologies (Cont.) Recovery Point Objective (RPO) oPoint in time to which systems and data must be recovered after an outage oAmount of data loss that a business can endure Recovery Time Objective (RTO) oTime within which systems, applications, or functions must be recovered after an outage oAmount of downtime that a business can endure and survive Recovery-point objectiveRecovery-time objective

© 2009 EMC Corporation. All rights reserved. Business Continuity Planning (BCP) Process oIdentifying the critical business functions oCollecting data on various business processes within those functions oBusiness Impact Analysis (BIA) oRisk Analysis oAssessing, prioritizing, mitigating, and managing risk oDesigning and developing contingency plans and disaster recovery plan (DR Plan) oTesting, training and maintenance

© 2009 EMC Corporation. 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

© 2009 EMC Corporation. All rights reserved. Business Continuity (BC) Planning Lifecycle Figure. BC planning lifecycle

© 2009 EMC Corporation. All rights reserved. Establishing objectives oDetermine BC requirements. oEstimate the scope and budget to achieve requirements. oSelect a BC team by considering subject matter experts from all areas of the business, whether internal or external. oCreate BC policies.

© 2009 EMC Corporation. All rights reserved. Analyzing oCollect information on data profiles, business processes, infrastructure support, dependencies, and frequency of using business infrastructure. oIdentify critical business needs and assign recovery priorities. oCreate a risk analysis for critical areas and mitigation strategies. oConduct a Business Impact Analysis (BIA). oCreate a cost and benefit analysis based on the consequences of data unavailability. oEvaluate options.

© 2009 EMC Corporation. All rights reserved. Designing and developing oDefine 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. oDesign data protection strategies and develop infrastructure. oDevelop contingency scenarios. oDevelop emergency response procedures. oDetail recovery and restart procedures.

© 2009 EMC Corporation. All rights reserved. Implementing oImplement risk management and mitigation procedures that include backup, replication, and management of resources. oPrepare the disaster recovery sites that can be utilized if a disaster affects the primary data center. oImplement redundancy for every resource in a data center to avoid single points of failure.

© 2009 EMC Corporation. All rights reserved. Training, testing, assessing, and maintaining oTrain 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. oTrain employees on emergency response procedures when disasters are declared. oTrain the recovery team on recovery procedures based on contingency scenarios. oPerform damage assessment processes and review recovery plans. oTest the BC plan regularly to evaluate its performance and identify its limitations. oAssess the performance reports and identify limitations. oUpdate the BC plans and recovery/restart procedures to reflect regular changes within the data center.

© 2009 EMC Corporation. All rights reserved. BC Technology Solutions oThe following are the solutions and supporting technologies that enable business continuity and uninterrupted data availability: oFault tolerant configuration oTo avoid single-point of failure oMulti-pathing software oBackup and replication oBackup recovery oLocal replication oRemote replication

© 2009 EMC Corporation. All rights reserved. Implementation of Fault Tolerance FC Switches Storage Array Redundant Network Clustered Servers Redundant Arrays Remote Site Redundant Ports Redundant FC Switches Redundant Paths Heartbeat Connection IP Storage Array Client

© 2009 EMC Corporation. All rights reserved. Multi-pathing Software oConfiguration of multiple paths increases data availability oEven with multiple paths, if a path fails I/O will not reroute unless system recognizes that it has an alternate path oMulti-pathing software helps to recognize and utilizes alternate I/O path to data oMulti-pathing software also provide the load balancing oLoad balancing improves I/O performance and data path utilization

© 2009 EMC Corporation. All rights reserved. Backup and Replication oLocal Replication oData from the production devices is copied to replica devices within the same array oThe replicas can then be used for restore operations in the event of data corruption or other events oRemote Replication oData from the production devices is copied to replica devices on a remote array oIn the event of a failure, applications can continue to run from the target device oBackup/Restore oBackup to tape has been a predominant method to ensure business continuity oFrequency of backup is depend on RPO/RTO requirements

© 2009 EMC Corporation. All rights reserved. Chapter Summary Key points covered in this chapter: oImportance of Business Continuity oTypes of outages and their impact to businesses oInformation availability measurements oDefinitions of disaster recovery and restart, RPO and RTO oBusiness Continuity technology solutions overview

© 2009 EMC Corporation. All rights reserved. Check Your Knowledge oWhich concerns do business continuity solutions address? o“Availability is expressed in terms of 9s.” Explain the relevance of the use of 9s for availability, using examples. oWhat is the difference between RPO and RTO? oWhat is the difference between Disaster Recovery and Disaster Restart? oProvide examples of planned and unplanned downtime in the context of storage infrastructure operations. oWhat are some of the Single Points of Failure in a typical data center environment?

© 2009 EMC Corporation. All rights reserved. #1 IT company For more information visit