A healthcare provider plans to store daily database backup archives in a secondary AWS Region to support their disaster recovery strategy. The database administrator suggests using Amazon S3 Glacier Flexible Retrieval with standard retrieval options, assuming that the archived data can be restored immediately during an unexpected primary site outage. Why is this assumption incorrect?
- Standard retrievals in Amazon S3 Glacier Flexible Retrieval typically take 3 to 5 hours to complete, which introduces significant recovery delays and prevents immediate data access.Answer
- BAmazon S3 Glacier Flexible Retrieval behaves as a pilot light environment, which requires a minimum of 24 hours to scale up compute instances before data blocks can be read.
- CData in S3 Glacier cannot be retrieved unless there is an active Amazon RDS Multi-AZ replication configuration actively mirroring the database transaction logs to the secondary Region.
- DRetrieval requests from S3 Glacier fail unless an Amazon Route 53 latency routing policy is configured to route the archive request to the nearest edge location.
Answer
Standard retrievals in Amazon S3 Glacier Flexible Retrieval typically take 3 to 5 hours to complete, which introduces significant recovery delays and prevents immediate data access.
The correct option is correct because standard retrieval requests in Amazon S3 Glacier Flexible Retrieval typically take between 3 to 5 hours to complete. For disaster recovery scenarios that require rapid recovery, this time delay is unacceptable, meaning the assumption of immediate restoration is incorrect.
Step-by-Step Solution
Key Concept
Disaster Recovery Storage Retrieval Times