As for EBS availability, we see a statement that redundancy is not required because it replicates within the same zone.
If my EBS fails, can I recover the instance from the replicated disk?
If possible, I'd like to know if it's done inside AWS or if it needs to be done manually.
If this is possible, I don't think I really feel the need for snapshots.
aws
The key points are availability and durability.
https://aws.amazon.com/jp/ebs/features/ #durabilityandsecurity
If you check here,
About Availability
Designed to maintain 99.999% availability
About Durability
Designed to provide an annual failure rate (AFR) of 0.1% to 0.2% depending on volume size and performance.In this case, "failure" refers to the complete or partial loss of the volume.
Availability is
Keep moving without interruption
Automatically running replication
"99.999%" means 365*24*60*60*0.00001=315.36 seconds of unavailable time per year.
And about durability, it's about whether your data can be maintained without corruption.
If you run 1000 volumes, one or two will be lost completely or partially.
If possible, I'd like to know if it's done inside AWS or if it needs to be done manually.
A. Replication occurs automatically, but can stop for 315 seconds per year.
You must ensure availability on your own.
If this is possible, I don't think I really feel the need for snapshots.
A. Why don't you check the need for snapshots in consideration of the percentage of one or two broken per 1000?
By the way, if it breaks, EBS support will start
"Your volume is the underlying hardware component
Failed due to multiple failures.Also, we were unable to recover it."
You may receive the message
© 2024 OneMinuteCode. All rights reserved.