A global financial analytics firm hosts a critical risk modeling application on-premises that generates massive datasets. The firm needs to migrate its storage backend to AWS. The architecture must store the generated datasets in a highly durable storage tier that is replicated to a secondary AWS region for disaster recovery (DR). The system must meet a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 10 minutes for accessing the DR datasets. The datasets must be immediately retrievable in the secondary region in the event of a primary region outage. Additionally, the on-premises application servers require low-latency, local cached access to the active datasets. Which storage architecture meets these requirements with the lowest recovery time and operational complexity?
- Deploy an Amazon S3 File Gateway on-premises to cache active datasets locally and store the primary data in an Amazon S3 bucket. Enable S3 Versioning and configure S3 Cross-Region Replication (CRR) with S3 Replication Time Control (S3 RTC) to a secondary region. In the destination bucket, use a lifecycle policy to transition objects immediately to the S3 Glacier Instant Retrieval storage class.Cevap
- BDeploy an AWS Storage Gateway Volume Gateway in cached volume mode on-premises. Configure volume snapshots to back up data to Amazon S3 in the primary region, and use S3 Cross-Region Replication to copy snapshots to the secondary region. Use an S3 Lifecycle policy to transition the replicated snapshots to the S3 Glacier Flexible Retrieval storage class, using Standard retrieval during a disaster.
- CDeploy an Amazon EFS File Gateway on-premises. Configure Amazon EFS Replication to copy data to a secondary region. Set up an Amazon RDS Multi-AZ DB instance in the primary region and create an RDS Read Replica in the secondary region, configuring the replica as the primary automatic failover target for database transaction records.
- DDeploy an Amazon S3 File Gateway on-premises. Configure S3 Same-Region Replication (SRR) in the primary region, and write a custom AWS Lambda function to copy objects to the secondary region's bucket. Set up the secondary region as a Pilot Light environment, relying on manual service activation to access the data during a failover event.