📢 Presentation: "Disaster Recovery on the AWS Cloud" Learn how AWS' technologies and industry-leading practises may assist your organisation in developing robust and resilient disaster recovery solutions. We will share knowledge and experiences in leveraging AWS services to ensure business continuity in the face of potential disruptions. 📌 Highlights of the presentation: Keynote Presentations: Gain a comprehensive understanding of the benefits, challenges, and best practices associated with building resilient systems. Workshop: Learn practical techniques for designing, implementing, and testing robust and scalable disaster recovery solutions on the AWS Cloud. Subscribe right away to always have our professional presentations! We have our own podcasts on YouTube: https://www.youtube.com/watch?v=g7vK3gJT12Q&ab_channel=ZenBitTech Follow us on Linkedin: https://www.linkedin.com/video/event/urn:li:ugcPost:7063805256597434369/

1. Disaster
Recovery on
AWS Cloud

2. 01
Adisasterisaneventthatpartiallyor
completelydisruptstheoperationsofoneor
moreapplications
Let's start with some
definitions:
02
Adisasternormallyrequireshuman
interventiontofailovertosecondarycopiesof
applicationsinordertomaintaintheir
functionality.

3. Human errors
Unintentional actions leading to a
security breach
Malicious attacks
Unauthorized actions that affect a
victim’s system such as DoS
Natural disasters
Technical failures
Environmental factors that cause a system
failure such as earthquakes or floods
A malfunction of software, hardware, or a
facility such as a power failure
What is a Disaster?
Is an event that partially or completely disrupts the operations of
one or more applications.

4. Why do you need
disaster recovery?
A properly planned and implemented disaster recovery solution helps mitigate
the following issues that can be caused by a disaster:
01
DirectandIndirectFinancialLoss: it is
critical for any revenue-generating
processes, as ustomers could switch to a
competing product.
02
ReputationalDamage: a short recovery
period can help avoid irreversible
damage to the corporate image.
03
FailurewithComplianceStandards:some
standards add very specific requirements,
like the minimal physical distance between
the source site and the disaster recovery site.

5. Expected Duration of the Disaster
How soon will the application recover
and how likely is the disaster to resolve
on its own?
Size of Impact
Which applications are affected and to
what extent is their functionality
impaired?
Geographic Impact
Tolerance of Downtime
This may be regional, national, continental,
or global.
How significant is the impact of the
application not functioning?
Common Factors and
Challenges There are several factors to consider when planning
your response to a specific disaster:

6. The six pillars of the Framework allow you to learn
architectural best practices for designing and
operating reliable, secure, efficient, cost-effective, and
sustainable systems.
Using the AWSWell-ArchitectedTool, available at no
charge in the AWS Management Console, you can
review your workloads against these best practices by
answering a set of questions for each pillar.
Are you Well-Architected?

7. Resiliency is a shared responsibility between AWS and the customer
AWS Responsibility

8. Disaster Recovery
and Availability
This approach is often referred to as “nines”, where a 99.9%
availability target is referred to as “three nines”. For your
workload, it may be easier to count successful and failed
requests instead of using a time-based approach.

9. Recovery objectives (RTO and RPO)
When creating a Disaster Recovery strategy, organizations most commonly plan
for the Recovery Time Objective (RTO) and Recovery Point Objective (RPO).
Recovery Objectives

10. Simple and repeatable testing
allow you to test more easily
and more frequently
Lower management overhead
decreases the operational
burden
Opportunities to automate
decrease the chances of error
and improve recovery time
Recover quickly from a disaster
with reduced complexity
Disaster recovery is different in the cloud

11. Disaster recovery strategies
To use cloud functionalities, this technique entails changing application architecture or design. Complex
programs employ this method, which may save money and enhance performance.

12. Backup and Restore
Backup and restore is a suitable approach for mitigating data loss or corruption.

13. AWS Services
AmazonElasticBlockStore(AmazonEBS)
snapshot
AmazonDynamoDBbackup
AmazonRDSsnapshot
AmazonAuroraDBsnapshot
AmazonEFSbackup(whenusingAWS
Backup)
AmazonRedshiftsnapshot
AmazonNeptunesnapshot
AmazonDocumentDB
AmazonFSxforWindowsFileServer,
AmazonFSxforLustre,AmazonFSxfor
NetAppONTAP,andAmazonFSxfor
OpenZFS.
AmazonElasticBlockStore(AmazonEBS)
volumes
AmazonEC2instances
AmazonRelationalDatabaseService
(AmazonRDS)databases(including
AmazonAuroradatabases)
AmazonDynamoDBtables
AmazonElasticFileSystem(AmazonEFS)
filesystems
AWSStorageGatewayvolumes
AmazonFSxforWindowsFileServer,
AmazonFSxforLustre,AmazonFSxfor
NetAppONTAP,andAmazonFSxfor
OpenZFS

14. Pilot Light Architecture
With the pilot light approach, you replicate your data from one Region to another and provision a copy of your
core workload infrastructure.

15. AWS Elastic Disaster Recovery Architecture

16. Warm Standby Architecture

17. Multi-site active/active
Multi-site active/active architecture (change one Active path to Inactive for hot standby)

18. AWS publishes our most up-to-the-minute
information on service availability on the
ServiceHealthDashboard.
A dashboard that shows recent and
upcoming events organized by category;
A full event log that shows all events from
the past 90 days.
The AWS Health Dashboard provides
information about AWS Health events that
can affect your account.
The information is presented in two ways:
A pattern to avoid is developing recovery
paths that are rarely executed.
For example, you might have a secondary
data store that is used for read-only queries.
When you write to a data store and the
primary fails, you might want to fail over to
the secondary data store. If you don’t
frequently test this failover, you might find
that your assumptions about the capabilities
of the secondary data store are incorrect.
Test disaster recovery implementation to
validate the implementation and regularly
test failover to your workload’s DR Region.

19. Conclusion
Create Recovery Time Objective (RTO) and
Recovery Point Objective (RPO) based on
impact analysis and risk assessments and
then choose the appropriate architecture to
mitigate against disasters.
Ensure that the detection of disasters is
possible and timely — it is vital to know when
objectives are at risk.
Ensure you have a plan and validate the plan
with testing.
Disaster recovery plans that have not been validated risk not being implemented due
to a lack of confidence or failure to meet disaster recovery objectives.

20. Join our Cloud Solutions Hub LinkedIn Group!
Contact us
We will be glad to answer on any questions!
Scan the QR-Code to get Lyudmila's
contacts and link to our Cloud
Solutions Hub LinkedIn Group!
Liudmyla Dziubynska
CTO at Zenbit Tech