Professional Documents
Culture Documents
REPEAT 1 Using Amazon EBS To Build Highly Resilient Applications CMP325-R1
REPEAT 1 Using Amazon EBS To Build Highly Resilient Applications CMP325-R1
© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Agenda
Amazon Elastic Block Store (Amazon EBS) overview
CloudEndure
© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Quick Amazon EBS overview & refresh
• Amazon Elastic Block Store
• EBS volumes & snapshots EC2
instance
• Virtual disks for virtual
computers
• Dependent on OS interaction
with block devices for storage
• Different types of volumes for EBS EBS EBS
different types of workloads volume
(boot)
volume
(data)
volume
(data)
Availability Zone
AWS Region
Matching Amazon EBS performance to Amazon EC2
performance
• EBS volume performance is
dependent on the EC2 instance
• EC2 families and sizes have
different aggregate EBS
capacities gp2 io1
General purpose SSD Provisioned IOPS SSD
• Mismatches between volume
performance and instance
capability can lead to
unexpected behaviors
• Oversizing EBS is neither
performance efficient nor cost
optimized st1 sc1
Throughput-optimized HDD Cold HDD
Common patterns for resiliency
• File-level recovery demands file-
level backups
• Snapshots in-region for volume
failure
99.999% service availability
• Snapshot copy x-region for
regional durability
• Cautions about mirroring and
striping
• Multi-volume consistent
snapshots 0.1% to 0.2% annual
failure rate (AFR)
Best practice: RAID
When to RAID?
• Storage requirement >16 TiB
EBS EBS EBS • RAID5/6 loses 20% to 30% of usable I/O to parity
What can you do with a snapshot?
EBS
snapshot
AWS Region
What can you do with a snapshot?
EBS EBS
snapshot snapshot
AWS Region AWS Region
© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Common cloud-based disaster recovery drivers
Threat of data loss due to Protect large-scale, DR site hardware DRaaS provider
ransomware and server compute-intensive refresh contract changes
corruption workloads
Cloud-based disaster recovery – Business outcomes
Robust operations
Achieve steadfast reliability and availability based on top-tier
recovery objectives
Operational efficiency
Obtain substantial cost savings by reducing the need for duplicate
infrastructure and licensing
Automated
• Easy failover and failback
Protection against
Failback to lightweight staging
ransomware,
cloud/on prem area reduces TCO
corruptions, and human
errors
How CloudEndure Disaster Recovery works
• CloudEndure continuously replicates any application or database from any source into AWS
• Business outcome: Use AWS to significantly reduce DR TCO while improving recovery objectives
Oracle
Database Oracle
Database
Microsoft Microsoft
SQL Server SQL Server
Wide platform support*
Worldwide Flight • Needed to meet aggressive recovery targets for compliance with government security guidelines
• Deployed DR solution for all busy servers, including SQL and IBM MQ servers
Services (WFS) • Success with DR project prompted decision to migrate entire production environment to AWS
© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.