Business Resiliency For Cloud Services

BUSINESS RESILIENCY
FOR CLOUD SERVICES
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Business Resiliency for Cloud Services
© Copyright 2021 Dell Inc. Page i

Table of Contents
Business Resiliency for Cloud Services ............................................................................... 2
Business Resiliency Overview ................................................................................. 3

Business Resiliency Overview ............................................................................................. 4
Why Resiliency Matters........................................................................................................ 5
What a Resilient Business Requires .................................................................................... 7
Evolution of Business Resiliency.......................................................................................... 8
Evolution: Site Recovery ...................................................................................................... 9
Evolution: DRaaS............................................................................................................... 10
Evolution: Application Continuity ........................................................................................ 11
Evolution: Resiliency-as-Code ........................................................................................... 12
Resiliency Maturity: Key Elements ..................................................................................... 13
Resiliency Maturity: Ratings ............................................................................................... 15
Business Resiliency Capabilities: Summary ....................................................................... 17
Knowledge Check .................................................................................................... 18

Question 1 ......................................................................................................................... 19
Business Resiliency Capabilities and Considerations ......................................... 20

Business Resiliency Capabilities and Considerations......................................................... 21
Business Continuity and Data Protection ........................................................................... 22
Disaster Recovery.............................................................................................................. 23
DR Considerations ............................................................................................................. 25
Cloud-Based Backup or Backup as a Service .................................................................... 26
Cloud-Based Backup: Considerations ................................................................................ 27
Concepts in Practice: Data Protection ................................................................................ 28
Data Security ..................................................................................................................... 31
Concepts in Practice: Dell EMC PowerProtect Cyber Recovery ......................................... 32
Artificial Intelligence for IT Operations (AIOps) ................................................................... 34
AIOps Benefits ................................................................................................................... 35
AIOps Considerations ........................................................................................................ 36
Page ii © Copyright 2021 Dell Inc.

Knowledge Check .................................................................................................... 37
Question 1 ......................................................................................................................... 38
NanCo Case Study ................................................................................................... 39

NanCo Case Study ............................................................................................................ 40
NanCo Case Study ............................................................................................................ 41
NanCo Case Study: Discussion Area ................................................................................. 42
Proven Professional Certification ....................................................................................... 43
You Have Completed This eLearning ................................................................................. 44
Appendix .................................................................................................... 45
© Copyright 2021 Dell Inc. Page iii

Business Resiliency Overview
© Copyright 2021 Dell Inc. Page 1

Page 2 © Copyright 2021 Dell Inc.



Why Resiliency Matters
The 21st century digital IT requires that the application, data and infrastructure
services are reliable, always available, serviceable, and security implemented by
design. In a typical organization today, users interact with multiple systems hosted
internally and externally to perform their job. As the number of systems, users, and
data grows to run the business, so too does the complexity and the necessity of
business resilience.
First, let us take a look at why resiliency matters and how it impacts organizations.
Consider the ‘The Global Data Protection Index1’ survey by Dell.
From this survey, it is found that the most organizations are still behind the curve
and are susceptible to unplanned downtime, data loss and suffer monetary loss. In
addition to financial impact, disruptions also result in loss of productivity, time to
market, fines, and reputational loss.
1
The Global Data Protection Index is a Dell survey to over 1000 IT decision
makers and organizations ranging from public and private sectors across the globe.
The intent of this survey is to directly hear from the customers and understand their
challenges. So that Dell Technologies can improve their products, solutions, and
services and help our customers meet their business objectives.

Click here to learn more about the opinions of customers about business resiliency.

What a Resilient Business Requires

PREPARE ALIGNED TO
For Emerging Threats Enterprise-Wide Risk Management
ZERO INTEGRATED MULTI CLOUD &

TRADITIONAL IT
Downtime & Lost Transactions

Security and Governance
CONTINUOUS
Application Availability
Resiliency is about organizations aligning their security, data protection, and

availability with business priorities and enterprise risks. It ensures that business
process is tied to applications, not just at the storage and infrastructure layer, is
always available despite the impact of disruptions.
Organizations must be better prepared for the emerging threats. It is imperative

that organizations should fully understand and capture the requirements of
enterprise-wide risks, threats, and dependencies before aligning an IT strategy and
roadmap.
Click here to know the goals of organizations, including the board and their CIOs.

Evolution of Business Resiliency
Build Test Release
Site Recovery Application Continuity Resiliency-as-code
Evolution of Business Resiliency
Today, organizations must protect their businesses from natural disasters and
man-made errors. With the evolution of technology, there has to be significant
changes in the way organizations plan their business continuity strategies to
establish resiliency. The focus shifts from complete site recovery to the continuing
operation of a business using application continuity, and resiliency-as-code.

Evolution: Site Recovery
A few years ago, options to establish resilience were limited and typically involved
having a second physical data center/ DR site that is located at a different site or
region. All the data and applications were replicated to the secondary data center.
If there is a disaster or unexpected event, the entire business operations would
resume from the secondary data center.
A few disadvantages that are involved with this approach include:
• Expensive and Time-consuming: Organizations had to build a second data

center where all the data from the primary site will be replicated to the new site.
This made the solution unattainable for many smaller and medium size
organizations.
• Unreliable: The process is complex as there is no automation, and the
secondary site requires to be monitored and tested regularly. Any manual errors
could have a severe impact on the business. Sometimes, the full site recovery
may not be tested at scale or under real conditions.
• Maintenance: Organizations are always responsible for managing and
operating their own DR solution and also to maintaining their IT environment.
This poorly designed DR solution would usually end up affecting RTOs and RPOs,
due to high latency or improper configuration of network and other infrastructure
components.

Evolution: DRaaS
The traditional approach was then replaced by Disaster Recovery as a Service

(DRaaS) with the rise of cloud computing for flexibility, ease of deployment, cost,
and recovery times benefits. This cloud-based solution helps organizations to
implement robust and comprehensive DR strategies with limited budget and not
much of an IT management required.
This solution allowed organizations to back up their data and infrastructure in a

cloud computing environment managed by a third-party service provider. If there is
a disaster, organizations continued to run their applications from the cloud
environment almost instantaneously. Organizations purchased DRaaS plans
through a subscription model or pay-per-use model.
A few considerations with this solution include:
• Organizations should understand the service level agreement implications of

the following:
− What happens if both the organization’s and provider’s facilities are affected
by the same disaster?
− Review different policies of the provider on which customer gets help first in
case of a large regional disaster.
• As this solution may vary in scope and cost, organizations must carefully
evaluate and choose the service providers that meet their needs and budget.
Click here to know the disadvantages with this approach.

Evolution: Application Continuity
Apart from natural disasters, organizations may Current State - Full-site only
Primary Secondary
often face partial outages due to application failure,
component or rack failure, and/or cyberattacks
where the outage is at a smaller scale. In such
scenarios, organizations can:
• Decide not to implement full site recovery as it Future State - Application Continuity
can be risky and time consuming. Primary Secondary
• Use resiliency strategies such as application

continuity.
In this strategy, if there was a loss of network

connection to a couple of cabinets, only the
impacted applications from the cabinets would be
relocated/failed-over to an alternate site. This takes less time than relocating the
entire data center.
Click here to learn about the considerations with this approach.

Evolution: Resiliency-as-Code
The application continuity concept can be further implemented with resiliency-as-

code, which uses infrastructure-as-code to completely repave applications with
automated pipelines in a software defined modern datacenter.
This approach can even be used to rebuild an entire data center, if needed to
recover from extreme cyber events, such as ransomware attacks. CMDBs can be
actively maintained while issues, such as configuration drift, can be resolved in this
model because everything is automated and updated to all known targets.

Resiliency Maturity: Key Elements
Click each tab to view details about the key elements that are used to assess
organizations on where they stand regarding implementing resiliency in their
business.
Organizational Readiness
• Executive management that is committed to corporate resiliency efforts

• Strategic and tactical program planning process
• Key personnel trained and ready to respond
• Emergency response and crisis communications plans developed and tested
• Existence of a formalized training and awareness program
Alternate Site Adequacy
• Alternate site capable of supporting business operations based on pre-

established function, performance, and capacity criteria consistent with
application prioritization
• Adequate hardware, software, network, and security infrastructure
Reliability Assurance Exercise and Validation
• Formalized alternate site exercise and validation program

• Rigorous testing objectives and detailed success criteria defined
• Environment performing as expected
• Adequate support personnel, management, and process execution
• Attainment of major test, RTO, and RPO objectives
• Acceptable systems management and monitoring
• Assurance that plans are executable.
Business and IT Alignment
• Impact of service disruptions understood, documented and communicated

• Application environments prioritized and tiered based on RPO and RTO

requirements
• Application and system flow and interdependencies mapped
• Mitigation strategy approved by executive management
Documentation and Process Maturity
• Current, complete and comprehensive documentation for technology

restoration, policies and procedures
• Scalable, repeatable process defined to accommodate business growth and
increasing recoverability requirements
• DR program metrics and reporting capabilities support continuous improvement
Risk and Threat Mitigation
• Threats and risks understood, ranked, and documented based on probability

(location, region, climate, so on)
• Executable mitigation strategies defined, communicated, and approved by
management, including any exclusions
Cost and Risk Balance
• Program expenses in line with defined corporate strategic and tactical goals and
objectives relative to addressing potential impact scenarios and mitigating
identified operational risks
• Cost-benefit analysis of available alternatives directly linked to business or
technical, expanding or contracting requirements and linked to increasing or
decreasing impact and risk; Expense that is tracked and regularly reported
Audit and Compliance
• Regulatory compliance and audit reporting requirements are well defined and
understood.
• Open program issues are tracked and remediated; Monthly and quarterly
reporting obligations satisfied.

Resiliency Maturity: Ratings
Based on the key elements assessed, organizations can be rated for business
resiliency.
Click each level on the image to learn more.
Business Resiliency Maturity
1 2 3 4 5 6
1: The control element has not yet been developed, or there is no evidence that
control element exists. Exposure to extensive service outage and the impact to the
company is catastrophic.
2: The control element is at its infancy. The approach to disaster recovery is

limited, or ad hoc with limited oversight, unclear ownership, without communication
between teams, and employees are unaware of their roles and responsibility.
Exposure to prolonged outage and the impact is catastrophic.
3: The program is evolving and gradually improving. Processes are not

documented, or evaluated regularly. The approach to DR is changing, with some
oversight, unclear ownership, with limited communication between teams, and
employees may not be aware of their roles and responsibility. The control elements
are intuitive, and the impact can be severe.
4: The DR control elements are in place and are adequately documented.

Independent oversight and ongoing review and testing of plans are not
evident. Critical services are defined and corporate Recovery Point objective
(RPO) and Recovery Time Objective (RTO) baseline is established. The approach
to business continuity is defined and in place, with adequate senior management
oversight, clear ownership, with communication between teams, and employees

are aware of their roles and responsibility. The program is measurable, and the
impact is moderate.
5: The DR control elements are in place, and formal BC plan are documented and
tested frequently. Evident senior management oversight and active participation in
the BCM Program. Ongoing review and testing of plans are documented. Ongoing
communication between internal teams and external entities is in place, and
employees are aware of their roles and responsibility. The control elements are
measurable, and the impact is low.
6: Effective DR control elements are in place company-wide, formal BC plans are

documented and tested on regular basis, and lessons learned are documented and
reflected on the BC plans and future test plans. Senior management is actively
engaged and participates on all mock disaster exercises, and meets regularly to
evaluate the BCM Program. Mock disaster exercises are end-to-end and involve
external entities. Ongoing communication between internal teams and employees
is aware of their roles and responsibility. The metrics are measurable, and the
impact is low.

Business Resiliency Capabilities: Summary
Establishing resiliency involves implementing a broad range of capabilities

including building a wide range of availability and disaster recovery, business
continuity, and security strategies thus ensuring confidence in recovering from any
type of outages.
Organizations can use cutting edge technologies, process, programs, and

methodology to meet their business and regulatory objectives that are involved in
establishing resiliency capabilities.

Knowledge Check
Knowledge Check

Knowledge Check
Question 1
1. Select the capabilities required for the IT organizations to run a resilient

business.
a. Prepared for emerging threats
b. Integrated multi-cloud and traditional IT
c. Maximum downtime and a few lost transactions
d. Infrastructure and application silos
e. Data protection silos

Business Resiliency Capabilities and Considerations


Business Continuity and Data Protection
Business Continuity
• Enables continuous availability of information and services for failure of SLA
requirements
• Involves proactive measures such as business impact analysis, risk
assessment, building resilient IT infrastructure, deploying data protection
solutions
• Involves reactive countermeasures, such as disaster recovery
• Ensures information availability as a primary goal
Data Protection
• Organizations using multiple cloud environments face
challenges with having multiple data protection strategies
leading to data protection silos.
• Regardless of the complex multi-cloud environment, the
goal of organizations should be to protect all the
components. These components include physical and
virtual resources that are deployed across private and public clouds.
• A more efficient strategy is to deploy a single data protection solution. This
solution includes backup, remote replication, archive, and disaster recovery
mechanisms for both on-premise and public cloud environments.

Disaster Recovery
With the growing transition to cloud computing, many

organizations are looking to leverage the cloud to enhance
their disaster recovery (DR) plan. A comprehensive DR plan
should include infrastructure components, potential threats,
most critical applications, and the order of their recovery.
Adopting cloud services in the disaster recovery plan allows
an organization to design a cloud-based DR plan and
automate the recovery processes.
Click ‘arrow marks’ or ‘dots’ to navigate through each option to learn about
the steps involved in an effective DR plan.
Assess Current IT Environment and Identify Gaps
• An organization should assess their

current IT environment, and identify
potential threats and risk factors.
• Discover vulnerabilities and identify
which applications and business
functions are critical.
• Perform business impact analysis to
understand how service disruption might
affect the business.
These assessments would help in better

understanding the financial, and non-
financial costs involved associated with a DR event.

Plan and Design DR Measures
• Implement all DR measures such as

mechanisms to reduce security risks.
• Document the process of what the
organization must do during an actual
disaster, and strategy used to recover
the infrastructure.
• Implement data protection solutions that
meets the needs of an organization to
achieve the DR objectives.
Test and Implement DR Plan
• Run regular tests to verify if the DR plans

actually work.
• Test whether all the critical applications
can be recovered as per the expected
time period.
• Identify any discrepancies or issues with
the current plan and if needed, update
the plan to achieve the desired results.

DR Considerations
A few considerations for DR planning include:
• It is important to commit to implementing all the strategies identified in the DR

plan.
• Training and awareness must be created to ensure that the entire organization
is confident and has the required skills to implement the plan.
• Use back-up and replication techniques for effective DR implementation.
− Decide where all the data gets stored (local devices or central server) so
that all the files are included in the backup.
− Classify data based on their criticality and define the associated metrics for
retention and archival.
− Disaster comes in many forms. Implement data protection mechanisms to
avoid data loss and downtime.
• Thoroughly test the DR plan to discover issues such as configuration details,
license key, application dependencies. Frequently testing the DR plan will help
to make the plan robust and improve confidence in it.
• Orchestrate and automate the DR plan. Ensure that the code can be
customized and scripted based on the requirements.

Cloud-Based Backup or Backup as a Service
• Cloud-based backup or backup as a service enables organizations to procure

backup services on-demand in the cloud.
• Organizations can keep a local backup copy in their private cloud and use a
public cloud for keeping their remote copy for DR purpose.
• For providing backup as a service, organizations and service providers should
have necessary backup technologies in place to meet the required service
levels.
Some organizations prefer a multi-cloud cloud option for their backup strategy.

Cloud-Based Backup: Considerations
A few considerations for a cloud-based backup include:
• Choose the Backup Location Wisely: Backup location determines how

accessible and better protected the assets are. The best practice is to use
multiple cloud environments within the same country but located in different
geographic regions. Moving data across international boundaries could create
unnecessary legal and regulatory complications.
− Choose at least two different cloud providers in the backup and recovery
strategy.
• Data Availability and Criticality: Usually cloud-based backup does not allow
to make changes in real-time. Any changes can be updated by replacing the
exiting file with a new one. Hence, this approach is suitable for non-production
data. It is also important to ensure that the uptime levels will be met by the
provider for continuous availability of data.
• Data Transfer Constraints: Different service providers use different protocols
for data transfer and the rate at which the data gets transferred may also vary
from provider to provider. Also, some providers may restrict on the amount of
data or file size that can be transferred at a given time.
• Security: Ensure that the service provider implements necessary security
mechanisms to secure the data in cloud and in-transit. Also, ensure that the
security levels mentioned in the SLA are met by the provider.
• Data Recovery/Destroy on Contract Termination: Organizations must ensure
that the provider either recovers or they destroy (physically and electronically)
the data when the contract is terminated.

Concepts in Practice: Data Protection
Click ‘arrow marks’ or ‘dots’ to navigate through each option to learn about
the Dell EMC products for data protection.
Dell EMC Cloud Disaster Recovery
• For organizations looking to the cloud as a disaster recovery option, Dell EMC
Cloud Disaster Recovery (Cloud DR) can be a solution. This product allows
enterprises to copy backed-up VMs from their on-premise back-up servers to
the public cloud, such as AWS, AWS GovCloud, Azure. This method helps to
orchestrate DR testing, failover, and failback of cloud workloads in a disaster
recovery scenario.
• These workloads can be run directly in the public cloud. Therefore, full
deployment of the on-premises data protection solutions in the cloud is not
required in order to protect and recover your VMs.
• Delivers a consistent experience by extending the existing on-premises data
protection to the cloud. This way that it delivers a familiar user experience, thus
requiring minimal education and training, and direct in-cloud access, monitoring
and reporting.
• The restore servers within the cloud are spun up only if the primary data center
is not available and decommissioned when no longer needed. This way that it is
more cost-effective than having hardware up and running within the public
cloud.
Dell EMC PowerProtect Data Manager
Dell EMC PowerProtect Data Manager enables organizations to protect, manage

and recover data on-premises, virtualized and cloud deployments with self-service
capabilities. It offers operational efficiency, and IT governance controls to ensure
compliance.
Key features include:
• Software defined with built-in deduplication for data protection, replication, and
reuse
• Self-service for data owners combined with central IT governance

• Multi-cloud optimized with built-in cloud tiering

• PowerProtect Central, a SaaS-based management, compliance and predictive
analytics platform
• Modern services-based architecture for ease of deployment, scaling and
upgrading
Dell EMC PowerProtect Cloud Snapshot Manager
• Cloud Snapshot Manager (CSM) is a SaaS solution that makes it easy to

protect workloads in public cloud environments without requiring any installation
or infrastructure.
• Customers can discover, orchestrate and automate the protection of workloads
across multiple clouds based on policies for seamless backup and disaster
recovery.
• CSM breaks cloud silos, allowing customers to use one tool to protect
workloads across multiple clouds.
• Designed for any size cloud infrastructure, CSM provides global visibility and
control to gain insights into data protection activities across the entire cloud
infrastructure.
Dell EMC PowerProtect Appliance – DP
• PowerProtect DP series appliance is a comprehensive backup, replication,

recovery, and cloud-ready solution for physical and virtual workloads.
• PowerProtect Appliance is the next generation of Integrated Data Protection
Appliance (IDPA) that converges data protection storage, protection software,
search, and analytics into an integrated solution.
• Available in different configurations, meeting the requirements of SMB to mid-
size enterprises, and large size enterprises.
• Requires three license files namely protection storage (Data Domain), backup
server (Avamar), and reporting and analytics (Data Protection Advisor).
Dell EMC PowerProtect DD
• Data Domain (DD) series enables organizations to protect, manage and recover
data at scale across their diverse environments.

• It is the next generation of Dell EMC Data Domain appliances, that are now
setting the bar for data management from edge to core to cloud.
• DD series provides storage capacity up to petabytes of capacity for long-term
retention in the cloud, with Dell EMC Cloud Tier.
• DD series provide fast disaster recovery with orchestrated DR and provide an
efficient architecture to extend on-premises data protection.
• PowerProtect DD Virtual Edition (DDVE) enables data protection in the cloud
for applications running in the cloud.
− DDVE in the cloud allows for both backup and replication.

− Data can be moved to an on-premise PowerProtect DD and backup to the
cloud, or even backup and replicate data between two instances of DDVE
running in the cloud or on-premise.
− This allows multiple DDVE instances to be spun up in other regions and
backup and replicate the data over to keep everything consistent.

Data Security
Data security is always a top priority for IT organizations.

When adopting a multi-cloud strategy, organizations must
adopt a mix of security mechanisms to strengthen the
resilience of cloud environments.
• A crucial component of cloud security is data integrity.

Implementing access control and least privilege principle
to access multi-cloud infrastructure are important. Another
best practice is to regularly monitor the user activity, failed access attempts, and
modification of data.
• Ensure data confidentiality by discovering and categorizing the data and
implementing encryption techniques. It is important to understand what data
needs protection and where it resides to set priorities and apply appropriate
security controls.
• Ensure data availability by implementing fault tolerance and application
availability methods.
− Also, ensure that the service provider offers an SLA that meets the
organization’s availability requirements.
− As the multi-cloud operating model itself acts as a strategy to improve
availability, be sure to synchronize the security policies and settings across
service providers.

Concepts in Practice: Dell EMC PowerProtect Cyber Recovery
Dell EMC Cyber Recovery solution protects the most critical data in a vault
environment. The vault is ideally physically isolated, a locked cage or room, and is
always logically isolated using an operational air gap. The vault components are
not accessible from production and access to the vault target when the air gap is
unlocked is extremely limited. This is a key to the maturity of our solution. The vault
is not an extra data center, it is usually located at the production or corporate data
center and more frequently now, with a third party solution provider.
The vault operates in four basic steps. Click the step number on the image to
learn more.
Cyber Recovery Process
1: Data representing critical applications are synced through the air gap, which is
unlocked by the management server into the vault and replicated into the vault
target storage. The air gap is then re-locked.
2: A copy of that data is made. Vault retention is configurable, but most keep about
a month's worth of copies.
3: The data is retention locked to further protect it from accidental or intentional

deletion.
4: The data is optionally analyzed by an analytics engine called CyberSense.

Recovering data from the vault in the event of a cyber-attack or simply for recovery
testing procedures is critical and there are several ways recovery can be
performed. Monitoring and reporting is also provided from within the vault and can
be shared outside of the vault environment in various secure methods.

Artificial Intelligence for IT Operations (AIOps)
AIOps
In a multi-cloud environment, the organizations have the flexibility to scale their

infrastructure rapidly based on the demand. However, they face challenges with
managing the large amounts of data that must be captured, processed, and acted
on to derive business value. As the data volumes and the systems that are used to
manage that data grow, it becomes challenging for the IT staff to identify or predict
the system performance or failures. This can impact the operational resilience and
availability.
Harnessing advanced technologies, such as AI, machine learning, and Big data, to
equip IT staff with more intelligence to identify and resolve critical outages is
becoming extremely important.
This is where AIOps (Artificial Intelligence for IT Operations) can deliver significant
value.

AIOps Benefits
AIOps is the implementation of machine learning and big data technologies to IT

operations challenges. AIOPs platforms combine the various data from multiple
sources such as monitoring tools, logs, ticketing system and so on. They consume
and analyze this huge amount of data and present valuable results, such as alerts,
after which the IT teams can take actions.
Example of AIOps platforms: Moogsoft 2
Benefits of AIOps:
• Helps IT teams to identify the root causes of outages and performance issues
by breaking down data silos with full visibility across IT environments.
• Improves IT productivity by automating and accelerating various processes
such as technical-support functions so that the IT teams can focus on more
valuable work.
• Enhance IT operations by delivering greater insights with the use of machine
learning, data science, and visualization techniques.
2
It is designed to greatly reduce IT alerts and ticket volumes, suggest root causes
and enable cross-team collaboration to solve incidents faster.

AIOps Considerations
Organizations planning to use AIOps to accelerate innovation and momentum of AI

in their IT operations should focus on following considerations:
• Implementing AIOps should have specific goals.

− Example: Discover how often alerts are created in their IT environment and
whether they require automation, analysis, and remediation.
• Use the right monitoring and performance tools to gather the right data because
machine learning algorithms will only be as good as the data they receive.
• Organizations must decide how they will use the AIOps platforms in order to
budget for the features. Examples include:
− Depth: Determine the breadth of functionality required.

− Range of supported use cases: Monitoring and basic data analytics, cost
and capacity planning, determining the impact of an IT disruption on the
business, and security operations.
− AIOPs tools: Some AIOps tools, such as data-agnostic tools, can work with
any type of data which costs more compared to other AIOps tools, such as
domain-centric tools, which work with only certain types of data and use
cases.

Knowledge Check
Knowledge Check

Knowledge Check
Question 1
1. Which Dell EMC product protects the most critical data of an organization in a
physically isolated room?
a. PowerProtect Cyber Recovery
b. PowerProtect DD
c. PowerProtect Data Manager
d. PowerProtect Appliance - DP

NanCo Case Study
NanCo Case Study

NanCo Case Study
NanCo Case Study

NanCo Case Study
NanCo Case Study
Click the
NanCO Art Services Company link below
to
understan
d the
multi-cloud
requireme
nts of
NanCo.
• Scenar
io

NanCo Case Study
NanCo Case Study: Discussion Area
The Online Course Contains an Interaction Here.
[Detailed description of the Interaction for Guides]

NanCo Case Study
Proven Professional Certification
Cloud Architect
Available for all audiences, the cloud architect certification journey begins with
either the CIS course or the ISM course. CIS provides fundamental details about
digital transformation and the critical role of cloud computing. ISM provides
comprehensive details for various infrastructure components in a modern data
center environment. The specialist level CIPD course focuses on cloud
infrastructure including: CI/HCI, cloud management platform, application
development and deployment platform, plus hybrid and multi-cloud. The expert
level Cloud Services Management curriculum concentrates on IT transformation,
service lifecycle and management, workforce transformation, multi-cloud strategy,
cloud operating model, cloud-native application development, and business
resiliency.
Cloud Architect,
Cloud Services
Transforming Traditional IT to Digital IT

Cloud Services Lifecycle and Management
Cloud Services Management Workforce Transformation for Cloud Services
Multi-Cloud Strategy for Cloud Services (ODC)
(C, VC) Cloud Services Operating Model
Cloud-Native Application Development
Cloud Architect, Cloud

Infrastructure
Cloud Infrastructure Planning and Design

(C, VC, ODC)
Cloud Infrastructure and Services Information Storage and Management
Cloud Infrastructure and Services Information Storage and Management

(C, VC, ODC) (C, VC, ODC)
(C) - Classroom
(VC) - Virtual Classroom
(ODC) - On Demand Course
For more information, visit: http://dell.com/certification

NanCo Case Study
You Have Completed This eLearning
Go to the next eLearning or assessment, if applicable.

Appendix

Appendix
What Customers Say?

The results from the survey indicate the following:
• 82% Suffered from Disruptive Event: Unfortunately this metric has risen to
82% compared to previous years. Top reasons are unplanned systems
downtime such as technology failures from hardware, software, networks or
downtime related to process such as new changes in the environment.
Downtimes arising from a ransomware attack or other incident that prevented
access to data is also rising.
• 69% Lack Confidence in Recovery: Despite adoption of modern technologies
such as replication and multi-site datacenter architectures such as continuous
availability or high availability, we continue to see our customers are not well
prepared to recover from operational, cyber attack or a site wide failure. This is
mostly due to the monolithic nature of infrastructure and applications, weak
processes and poor planning which results in the inability to recover data. The
confidence measure is getting higher visibility with the Board and CxOs who are
concerned with reliably recovering all business-critical data in the event of a
cyber attack, fully recovering systems/data in the event of a data loss, meeting
backup and recovery SLAs and lastly compliance with regional data governance
regulations.
• 81% Concerned about Meeting SLAs: Majority of customers struggle with
ever-increasing volume of data that has put a strain on meeting SLOs for
recovering data in the event of data loss and lack Data Protection compliance.
Data volumes have increased by 39% between 2018 and 2019. Data Protection
operators are typically siloed and further away from the business, which
typically leads to not understanding the value of data and placing the proper
backup or archive strategy around it.
Overall, these numbers reiterate the necessity for Business Resiliency be a

required outcome of any IT transformation initiative.

Appendix
Business Resiliency Goals

• To prevent any downtime – planned or unplanned.
• To ensure that no transactions are lost.
• Organizations can harness a broader range of resiliency capabilities across
clouds models and still maintain a high level of security and governance similar
to traditional IT.
• Ensure continuous application availability.
Therefore, resiliency must be considered holistically across application availability,

data protection and preparing for emerging threats such as cyber attacks.

Appendix
DRaaS: Disadvantages
• With these traditional approaches, organizations are running all their
applications in one data center.
− Though they have built a secondary or DR site by investing a lot of money,
they are not using it until a disaster happens.
• This method results in inefficient use of IT assets and not suitable for modern
applications.
This is where application continuity comes into the picture.

Appendix
Considerations for Application Continuity

A few considerations with this approach include:
• It is proven to be reliable and helps in efficient use of IT assets.

• The process is granular and can be automated.
− Enables the granular movement of applications that are tied to specific
business processes to alternate data centers without requiring a site-wide
failover.
• Applications can run concurrently on several data centers, thereby reducing the
risk of any one data center or its component failure
− It significantly increases the ROI of all data center investments.
− It obsoletes the traditional DR strategy that was cumbersome and never
worked.
− The live testing benefit of moving applications periodically from one region to
another fulfills new regulatory requirements.
o Regulators are looking for “live test” versus mock DR tests in a bubble
that never represented a real life scenario
• Can be implemented for scenarios such as operational outage, disaster, and
cyber recovery.

Appendix
Scenario
As NanCo expanded their business across the globe, they have been facing challenges with respect to data loss and security which impacts them a lot in
terms of their financial aspect and reputation. Therefore, NanCo is looking to build resilient capabilities for their infrastructure and operati ons to meet the
required SLAs.
NanCo’s senior management including the board and their CIOs, have come up with goals aligningto their business resiliency strategies. These goals
include:
1. Prevent any downtime – planned or unplanned.
2. Ensure that no transactions are lost.
3. Maintain a high level of security and governance for cloud-model that is similar to traditional IT.
4. Ensure continuous application availability.
To achieve these goals, NanCo has the following requirements:
1. They need a cloud-based disaster-recovery solution, as their current disaster recovery solution is inefficient with the expanding business
2. They don’t have budget to build and manage their own backup infrastructure to protect their data. They need a solution to reduce the complexity of
managing the backup environment.
3. NanCo’s business is expanding and the amount of data and IT systems are increasing exponentially. This impacts the operational resilience and
availability. NanCo need a solution to better manage this solution and run a smooth operation.
With these challenges and requirements, NanCo needs help from the consulting firms to obtain the solutions.


Business Resiliency For Cloud Services - Participant Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Business Resiliency For Cloud Services - Participant Guide

Uploaded by

Copyright:

Available Formats

BUSINESS RESILIENCY

FOR CLOUD SERVICES

© Copyright 2021 Dell Inc. Page i

Business Resiliency for Cloud Services ............................................................................... 2

Business Resiliency Overview ................................................................................. 3

Knowledge Check .................................................................................................... 18

Business Resiliency Capabilities and Considerations ......................................... 20

Page ii © Copyright 2021 Dell Inc.

NanCo Case Study ................................................................................................... 39

Business Resiliency for Cloud Services

© Copyright 2021 Dell Inc. Page iii

Business Resiliency for Cloud Services

© Copyright 2021 Dell Inc. Page 1

Business Resiliency for Cloud Services

Business Resiliency for Cloud Services

Page 2 © Copyright 2021 Dell Inc.

Business Resiliency Overview

Business Resiliency for Cloud Services

© Copyright 2021 Dell Inc. Page 3

Business Resiliency Overview

Business Resiliency for Cloud Services

Page 4 © Copyright 2021 Dell Inc.

Why Resiliency Matters

Business Resiliency for Cloud Services

© Copyright 2021 Dell Inc. Page 5

Business Resiliency for Cloud Services

Page 6 © Copyright 2021 Dell Inc.

What a Resilient Business Requires

For Emerging Threats Enterprise-Wide Risk Management

ZERO INTEGRATED MULTI CLOUD &

Downtime & Lost Transactions

Resiliency is about organizations aligning their security, data protection, and

Organizations must be better prepared for the emerging threats. It is imperative

Business Resiliency for Cloud Services

© Copyright 2021 Dell Inc. Page 7

Evolution of Business Resiliency

Build Test Release

Site Recovery Application Continuity Resiliency-as-code

Evolution of Business Resiliency

Business Resiliency for Cloud Services

Page 8 © Copyright 2021 Dell Inc.

Evolution: Site Recovery

A few disadvantages that are involved with this approach include:

• Expensive and Time-consuming: Organizations had to build a second data

Business Resiliency for Cloud Services

© Copyright 2021 Dell Inc. Page 9

The traditional approach was then replaced by Disaster Recovery as a Service

This solution allowed organizations to back up their data and infrastructure in a

A few considerations with this solution include:

• Organizations should understand the service level agreement implications of

Click here to know the disadvantages with this approach.

Business Resiliency for Cloud Services

Page 10 © Copyright 2021 Dell Inc.

Evolution: Application Continuity

can be risky and time consuming. Primary Secondary

• Use resiliency strategies such as application

In this strategy, if there was a loss of network

Click here to learn about the considerations with this approach.

Business Resiliency for Cloud Services

© Copyright 2021 Dell Inc. Page 11

The application continuity concept can be further implemented with resiliency-as-

Business Resiliency for Cloud Services