Question

Difficulty: MediumResilient and Highly Available Storage Infrastructure

A digital marketing agency maintains an on-premises file server containing active design assets and historical archives. The agency requires a hybrid storage solution that provides low-latency local read/write access to active assets while ensuring that all files are stored with high durability in the cloud. If the local data center suffers a catastrophic power failure, the agency must be able to resume file access for its designers within a Recovery Time Objective (RTO) of 1515 minutes, using either a secondary office or AWS-based compute instances. Which storage configuration meets these requirements?

  1. A
    Deploy an AWS Storage Gateway (Volume Gateway) in stored volume mode on-premises. Configure the gateway to backup point-in-time snapshots to Amazon S3 Glacier Flexible Retrieval, and retrieve them using Standard retrieval to construct new volumes at the secondary office.
  2. B
    Provision an Amazon EBS gp3 volume and enable EBS Multi-Attach to share the block storage concurrently between the on-premises servers and AWS EC2 instances, while relying on Amazon RDS read replicas to manage the failover process.
  3. Deploy an AWS Storage Gateway (Amazon S3 File Gateway) on-premises, and configure the local file server to mount the NFS file share backed by an Amazon S3 bucket. If the primary on-premises site fails, deploy a new S3 File Gateway virtual machine (VM) at the secondary office or on an Amazon EC2 instance, and associate it with the existing S3 bucket.Answer
  4. D
    Deploy an Amazon EFS file system using One Zone storage to host the design assets. Configure a Pilot Light disaster recovery strategy where the standby EFS file system in a secondary Availability Zone is kept inactive and only provisioned when a failover occurs.

Answer

Deploy an AWS Storage Gateway (Amazon S3 File Gateway) on-premises, and configure the local file server to mount the NFS file share backed by an Amazon S3 bucket. If the primary on-premises site fails, deploy a new S3 File Gateway virtual machine (VM) at the secondary office or on an Amazon EC2 instance, and associate it with the existing S3 bucket.
Deploying an AWS Storage Gateway (Amazon S3 File Gateway) on-premises allows designers to access files locally via NFS with low latency, while the master copy is stored in Amazon S3. In the event of a disaster, a new gateway VM can be quickly created on-premises at a secondary office or as an Amazon EC2 instance and pointed to the same S3 bucket. This restores file sharing capabilities in minutes, satisfying the 1515-minute Recovery Time Objective (RTO).

Step-by-Step Solution

1
Analyze the requirements for a hybrid storage solution that offers local caching and high cloud durability.
Identify that AWS Storage Gateway (Amazon S3 File Gateway) fits this scenario by caching active data locally while storing the primary copy in Amazon S3.
S3 File Gateway provides NFS/SMB access to objects in S3 with a local cache for low-latency read/write operations.
2
Evaluate the disaster recovery failover strategy against the 1515-minute Recovery Time Objective (RTO).
Determine that recreating the gateway virtual machine (VM) and pointing it to the existing Amazon S3 bucket allows immediate retrieval of file metadata and data access.
Since the file data is preserved in the S3 bucket, a new gateway can be quickly provisioned on-premises or on an EC2 instance without waiting for lengthy data restores.

Key Concept

AWS Storage Gateway (S3 File Gateway) hybrid storage and disaster recovery failover mechanics.
Estimated Time:2m 0s
Rate this question