A customer implemented AWS Storage Gateway with a gateway-cached volume at their main office.
You need to restore the Storage Gateway data in AWS.
How would you implement this?
Click on the arrows to vote for the correct answer
A. B. C. D.Answers - D.
Option A is incorrect because all gateway-cached volume data and snapshot data are stored in Amazon S3 encrypted at rest using server-side encryption (SSE) and cannot be visible or accessed with S3 API or any other tools.
(Ref: https://forums.aws.amazon.com/thread.jspa?threadID=109748)
Option B is incorrect because the lifecycle policy does not help to restore the data.
Option C is incorrect because the cached volumes are never stored in Glacier.
Option D is CORRECT because you can take point-in-time snapshots of gateway volumes made available in the form of Amazon EBS snapshots.
A new EBS volume can be created from the snapshot which can be mounted to an existing EC2 instance.
For more information on this topic, please refer to the AWS FAQs.
https://aws.amazon.com/storagegateway/faqs/To restore the data in AWS, the best approach will depend on the configuration and use case of the AWS Storage Gateway deployment.
In the given scenario, the customer implemented a gateway-cached volume at their main office. This means that frequently accessed data is stored in the local cache at the office, and less frequently accessed data is stored in Amazon S3. So, if data needs to be restored, it may be located in the Amazon S3 bucket.
Option A suggests using an HTTPS GET to the Amazon S3 bucket where the files are located. This could work if the data is readily accessible in the S3 bucket and can be downloaded directly. However, it may not be the most efficient option for large amounts of data or if the data is stored in an encrypted format.
Option B suggests restoring by implementing a lifecycle policy on the Amazon S3 bucket. A lifecycle policy can automatically transition data to Amazon S3 Glacier for archival or deletion based on rules that the user sets. While this can be a useful feature for managing data lifecycle, it may not be the best approach for restoring specific data quickly.
Option C suggests making an Amazon Glacier Restore API call to load the files into another Amazon S3 bucket within four to six hours. This option can be useful if the data is stored in Amazon Glacier and needs to be restored to S3 before it can be accessed. However, it may not be the fastest option for restoring data.
Option D suggests creating an Amazon EBS volume from a gateway snapshot and mounting it to an Amazon EC2 instance. This can be a good option if the data is stored in the gateway snapshot and needs to be accessed quickly. This option can provide faster access to data than downloading from S3 or restoring from Glacier, but it may not be the most cost-effective option for large amounts of data.
Overall, the best option will depend on the specific situation and needs of the customer. If the data is stored in the S3 bucket, option A may be the most straightforward approach. If the data is stored in a gateway snapshot, option D may provide the fastest access to the data. If the data is stored in Glacier, option C may be the most appropriate option.