Some common misconceptions around AWS backup and recovery include making all data public, giving instances excessive access, relying solely on AWS for updates, and ignoring file security. It is important to avoid these practices and back up EBS volumes regularly. EBS volumes come in SSD or HDD types with different performance characteristics and costs depending on workload needs such as transaction processing or large sequential data. Best practices for backup and recovery involve backing up EBS volumes regularly, saving configurations as templates, monitoring events and recovery processes closely.

1. The Miracle Of Aws Backup And Recovery.

2. Leave wrong ideas
Backup and recovery may be sometimes unescapable & one need to be organized leaving
away the wrong advices
Some of the widespread misconceptions
• Making the complete data public and providing the files downloading facility for securing of
files.
• giving the instance more access right
• Performing testing on specific things
• relying on amazon in case of updates
• Ignoring files security
One must get rid of above

3. Continuation...
Some wrong ideas may cause more disaster than the natural disaster or data
loss.
while taking the EBS volume through the EBS snapshots,sometimes we can
restore the most recent snapshot in order to restore the volume

4. EBS Classification
Amazon EBS provides four current generation volume types:
Provisioned IOPS SSD (io1),
General Purpose SSD (gp2),
Throughput Optimized HDD (st1) and
Cold HDD (sc1).
These volume types differ in performance characteristics and price, allowing you to tailor your
storage performance and cost to the needs of your applications. For more performance
information see the EBS product details page.
Select the most scalable volume type based on your purpose

5. Choosing the EBS volume
• Amazon EBS includes two major categories of storage:
• SSD-backed storage
• HDD-backed storage
SSD-backed volumes are designed for transactional, IOPS-intensive database
workloads, boot volumes, and workloads that require high IOPS. SSD-backed
volumes include Provisioned IOPS SSD (io1) and General Purpose SSD (gp2).
HDD-backed volumes are designed for throughput-intensive and big-data
workloads, large I/O sizes, and sequential I/O patterns. HDD-backed volumes
include Throughput Optimized HDD (st1) and Cold HDD (sc1).

6. Differences b/s SSD & HDD backed storage
SSD-backed storage
• Designed for transactional, IOPS-
intensive database workloads, boot
volumes, and workloads
• SSD-backed volumes include
Provisioned IOPS SSD (io1) and
General Purpose SSD (gp2)
• Require high IOPS
HDD-backed storage
• Designed for throughput-intensive and
big-data workloads, large I/O sizes, and
sequential I/O patterns
• HDD-backed volumes include
Throughput Optimized HDD (st1) and
Cold HDD (sc1).

7. Best Practices for backup and Recovery
• One should Regularly back up their EBS volumes
• Save the configuration as a template for launching future instances.
• When your instance restarts able to handle IP addressing .
• Events must be supervisioned.
• Process of recovering instances must be thoroughly monitored

8. For more on backup and recovery
To know more about AWS Backup and recovery in
depth,have a look on aws training

9. THANK YOU