Cloud Computing and Disaster Recovery

Transcription

1 Understanding the Cloud Environment Cloud Environment = Internet-based data access & exchange + Internet-based access to low cost computing & applications Cloud Computing and Disaster Recovery April 2013 Cloud Environment Characteristics: Software as a operations over a network Google Docs, Salesforce.com Cloud Models Platform as a Deploy customercreated applications to a cloud MS Azure, Amazon Web s On-Demand Self- as a Rent storage, processing, network and other computing resources Mozy, Rackspace Internet Accessibility Private Public Community Pooled Resources Elastic Capacity Usage- Based Billing Cloud Deployment Models Operated for a single organization Available to the general public or large industry group, owned by an organization selling cloud services Shared by several organizations, supporting a specific community 1 Understanding the Cloud Models Understanding the Cloud Deployment Models Software as a Less End User Provider applications are accessible through a thin client interface such as a web browser Provider manages/controls the infrastructure including network,, operating systems, storage, or individual application capabilities a third party and can be both on or off premise Allows an organization to act like a cloud provider internally Provides organization the flexibility to rapidly scale internal IT resources Provides organization with full control over data Often requires high initial investment but helps reduce long term costs More End User Control Platform as a Less End User E.g., Google Apps, MS Office Live, Netsuite, Salesforce Enables customer to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages/tools supported by the provider. Consumer does not manage/control cloud infrastructure but has control over deployed applications and possibly application hosting. E.g., Windows Azure, Force.com, Google App Engine Public Cloud: is owned by a cloud services provider, which makes it available to the general public or a large industry group Uses pay-as-you-go, utility pricing Provides high agility and speed-to-market Changes financial model from CAPEX to OPEX Offers less customer control over data and service levels Provides the opportunity to leverage the leading practices of an industry vertical or functional area More End User Control as a Provider offers quick deployment of computing resources such as processing, storage, and network Developers can write applications that run on the cloud Community Cloud: is shared by several organizations with common interestsoffering potentially the greatest transformational value of any of the Cloud deployment models. E.g., Amazon.com, Rackspace, Terremark, IBM 2 Often defined by industry, supply chains, or geography, supporting the emergence of new models and working relationships May be managed by the community or a third party; May exist on or off premise 3

2 IT Strategic Plan IT IT s Delivery IT Prog & Project IT Life Cycle Strategy Design Implement Operate Strategic ITSM Planning IT Financial IT Asset Security IT Continuity IT Governance IT Resource IT Portfolio Managment Portfolio Demand Impact Level Catalog Disaster Recovery Plan & Testing Availability Capacity SM Knowledge Validation & Testing Change Release & Deploy Configuration & Inv Plan Build Run Application & IT Assets Compliance Mgmt IT Quality Access Request Incident Supplier & Vendor IT Operations Problem Event & Perf Applications Servers & IT Controls IT s IT People IT Collateral Middleware Desktops Networks & Databases Mainframes Standards Compliance Mgmt IT s Support IT Operations Storage Facilities SD & NOC Rackspace Owner Vendor Manager Amazon Web s Google Liaison IT Finance Manager ( Provider for Retained s) Goals & Objectives 14% 30% 50% 0% 0% 0% 0% 0% 0% 0% 30% 50% 0% 0% 0% 0% 0% 30% Roles & Responsibilities 14% 0% 20% 0% 0% 0% 0% 0% 0% 0% 0% 20% 0% 0% 0% 0% 0% 0% Activites 14% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% Key Collateral 14% 0% 20% 0% 0% 0% 0% 0% 0% 0% 0% 20% 0% 0% 0% 0% 0% 0% 40% KPIs / Metrics 14% 50% 50% 0% 0% 0% 0% 0% 0% 0% 50% 50% 0% 0% 0% 0% 0% 50% Controls 14% 0% 30% 0% 0% 0% 0% 0% 0% 0% 0% 30% 0% 0% 0% 0% 0% 0% Continual Improvement 14% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% Dimension Score 5% 10% 0% 0% 0% 0% 0% 0% 0% 5% 10% 0% 0% 0% 0% 0% 5% Future State Logical Tools Architecture 25% 40% 30% 0% 0% 0% 0% 0% 0% 0% 40% 30% 0% 0% 0% 0% 0% 40% Tool Functionality 25% 20% 40% 0% 0% 0% 0% 0% 0% 0% 20% 40% 0% 0% 0% 0% 0% 20% 10% Tool Requirements 25% 30% 10% 0% 0% 0% 0% 0% 0% 0% 30% 10% 0% 0% 0% 0% 0% 30% Current State of Tools Implementation 25% 20% 30% 0% 0% 0% 0% 0% 0% 0% 20% 30% 0% 0% 0% 0% 0% 20% Dimension Score 3% 3% 0% 0% 0% 0% 0% 0% 0% 3% 3% 0% 0% 0% 0% 0% 3% Intent 9% 30% 0% 0% 0% 0% 0% 0% 0% 0% 30% 0% 0% 0% 0% 0% 30% 0% Commitment 9% 40% 70% 0% 0% 0% 0% 0% 0% 0% 40% 70% 0% 0% 0% 0% 40% 70% Policy Definition 9% 0% 50% 0% 0% 0% 0% 0% 0% 0% 0% 50% 0% 0% 0% 0% 0% 50% Policy Integration & Adoption 9% 60% 30% 0% 0% 0% 0% 0% 0% 0% 60% 30% 0% 0% 0% 0% 60% 30% Ownership 9% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 40% Scope 9% 0% 50% 0% 0% 0% 0% 0% 0% 0% 0% 50% 0% 0% 0% 0% 0% 50% Capability to Engineer ITSM Solution 9% 30% 60% 0% 0% 0% 0% 0% 0% 0% 30% 60% 0% 0% 0% 0% 30% 60% ITSM Engineering Resource Availability 9% 30% 10% 0% 0% 0% 0% 0% 0% 0% 30% 10% 0% 0% 0% 0% 30% 10% Adoption 9% 10% 60% 0% 0% 0% 0% 0% 0% 0% 10% 60% 0% 0% 0% 0% 10% 60% Project capabilities 9% 40% 0% 0% 0% 0% 0% 0% 0% 0% 40% 0% 0% 0% 0% 0% 40% 0% Step #1 Where to apply Cloud Delivery Models Choosing the appropriate Cloud delivery model begins with developing an overall vision of where and how the new models will be applied. This important step will enable IT leaders to drive the adoption of Cloud throughout the enterprise and prime the organization for success. Step #2 Enterprise Readiness for Cloud Adoption Private, Public, and Hybrid delivery models have different impacts and challenges for Enterprise IT organizations. A Readiness Assessment will prepare an organization to understand these challenges. Current State CRM BI Financial Technical Target State SaaS PaaS Dimensional Weight Capability Dimensions Capability Analysis Elements Element Weight IT Capabilities Strategy Generation Portfolio IT Financial Demand Level Catalog Capacity Availability ITSCM Information Security Supplier Transition Planning & Support Change SACM Release & Deploy Validation & Testing Evaluation Data Archiving Mgmt Compute Production Security & Regulatory Private Public IaaS Technology Cloud Readiness Assessment 4 5 Step #3 Transformation to an IT Integrator Operating Model Enterprise IT organizations that have successfully adopted Cloud delivery models have transformed their IT operating models to focus on integrating their internal and external IT services. This transformation should be holistic, taking into account the required process, organization, and technology elements as well as related risks, services, and financial aspects. Cloud for Disaster Recovery Technology provider processes integrator processes Governance change management Role of IT Technology standards and roadmap Integration and interoperability tools OPERATING MODEL TRANSFORMATION Governance IT ( Integrator) Risk s Finance IT Org Cloud Risks Mitigation strategy and controls framework Definition s IT Funding Model and chargeback allocation 6 7

3 Trends in Cloud BC-DR Cloud for Disaster Recovery (DR) continues to be a discussion for many of our clients. Cloudbased recovery services offer a way to achieve the recovery capabilities of advanced DR services at a more affordable, subscriptionbased price. There are concerns over security of the cloud but over time it will be a key component of disaster recovery program. The use of data replication technology continues to increase and Recovery Point Objectives (RPO) continue to lessen as end users tolerance for data loss diminishes Companies are reevaluating their DR plans for the virtual and cloud environments to address recovery complexity of applications and data spanning multiple architectures Banks are starting to use cloud computing services to manage disaster recovery Cloud services promise to save banks money and accelerate recovery time for smaller banks Only 3% of financial services companies in a recent Forester survey stated they had plans to implement cloud-based disaster recovery services in the next 12 months Recovery Objective Weeks Days Hours Minutes Seconds Traditional IT DR is still the preferred option if you want to retain full control of your environment and looking for Synchronous or Asynchronous replication Cloud DR service offerings are more geared towards filling the gaps between having a Hot Site or a Cold Site Cold Site Backup to Tape Using Cloud as part of your DR strategy should be based on Bare Metal two factors Complexity of your IT and Recovery Objective Restore Remote backup Cloud based recovery services Storage as a Warm Site Server virtualization or boot from SAN for rapid restart The graphic depicts the range of traditional IT-DR and Cloud based alternatives available laid out as a function of Recovery Objective and Cost. Backup as a Hot Site High Availability Clustering for automatic failover DR as a Application as a Asynchronous Replication Synchronous Replication 8 $ $$ $$$ Cost 9 Impact Analysis Changes Moving services to the Cloud will have downstream affect to an organization's BIA process Reconstructing process functions will be more complex as system interdependencies and data flow will change from traditional models Cloud Disaster Recovery Marketplace Example Providers Storage-as-a provider provides storage in the cloud through Amazon S3 integration with the clients own backup or replication EMC Atmos solution. Iron Mountain CloudRecovery Nirvanix Symantec Protection Network Backup-as-a Client data is backed up over the internet to the service EMC Mozy Pro provider. The client endpoints may have the service IBM BCRS providers agents or an appliance to facilitate backup. Iron Mountain Connected Iron Mountain LiveVault i365 SunGard Secure2Disk Symantec Protection Network DR-as-a- (virtual recovery) Application continuity-as-a- Client and data are backed up over the internet via end point agents or appliances. providers supports the backup and recovery of a specific application for the client, typically CA Instant Recovery On Demand I365 SunGard Virtual Server Replication Dell MessageOne Iron Mountain Total Suite - Forrester 10 11

4 Size Large Medium Cloud Recovery s Options Illustrative use cases of the Cloud Recovery s options across organization sizes. Small Cloud Disaster Recovery Options Storage as a Backup as a DR as a Application as Off-site backup and End user desktops archiving of data may decide based on need may decide based on need End user desktops End user desktops BCP / DR Cloud Considerations Opportunities Opportunity Variety of s Distributed deployment Lower RPO / RTO Enhanced SLA management Reduced providers offer many Cloud options that can be used by customers. These include: Storage-as-a-, Backup-as-a-, DR-as-a-, Application continuity-as-a-. Companies have the choice of selecting the right service driven by needs. Cloud environments inherently provide distributed architecture. These deployment models lower the risk that services are impacted by a site disaster. Cloud providers are able to provide lower the thresholds for RPO and RTO objectives through distributed architecture and data replication. Cloud provider SLAs can be leveraged to enhance in-house SLAs. For mission critical processes, these can be a significant advantage in the event of a disaster. Maintaining duplicate infrastructure can be very costly. Cloud providers have the capacity to adjust resources as they are being consumed BCP / DR Cloud Considerations Challenges Cloud Outage Considerations Challenge Security 3rd Party reliance Regulatory and Compliance Application specific versus process recovery Workforce management Shared infrastructure and potential data leakage are frequently mentioned risks that can negatively impact objectives. Transitioning key application / processes to 3 rd parties carries significant risks. A disaster that strikes Cloud providers can have significant downstream affect on clients. Challenges with various compliance initiatives can arise from Cloud deployments. Data storage and privacy requirements can be challenging to address when data is moved to the Cloud. Transitioning parts of the can allow for partial recovery; however, the recovery of all process dependencies can be challenging to address. In the event of a disaster that impacts personnel, IT systems alone do not provide a means to continuity. Reliance on 3 rd providers experience outages Level Agreements with 3 rd party reduce some of the risk ; however, an outage to a critical function can impact the organization beyond the outage period Continuity scenarios for a Cloud outage should be considered by service consumers Depending on the criticality of the Cloud service, organizations should develop Continuity plans in the event of a distribution of 3 rd party services factors should also be included as the communication between applications and services will be different than traditional in-house deployments 14 15

5 Cloud Outage Considerations Reliance on 3 rd providers experience outages Thank You! Level Agreements with 3 rd party reduce some of the risk ; however, an outage to a critical function can impact the organization beyond the outage period Continuity scenarios for a Cloud outage should be considered by service consumers Depending on the criticality of the Cloud service, organizations should develop Continuity plans in the event of a distribution of 3 rd party services factors should also be included as the communication between applications and services will be different than traditional in-house deployments Greg Bell Principal rgregbell@kpmg.com 16 17