A customer has a single 3-TB volume on-premises that is used to hold a large repository of images and print
layout files. This repository is growing at 500 GB a year and must be presented as a single logical volume. The
customer is becoming increasingly constrained with their local storage capacity and wants an off-site backup of
this data, while maintaining low-latency access to their frequently accessed dat
a. Which AWS Storage Gateway configuration meets the customer requirements?
A.
Gateway-Cached volumes with snapshots scheduled to Amazon S3
B.
Gateway-Stored volumes with snapshots scheduled to Amazon S3
C.
Gateway-Virtual Tape Library with snapshots to Amazon S3
D.
Gateway-Virtual Tape Library with snapshots to Amazon Glacier
B
0
0
answer is A
http://docs.aws.amazon.com/storagegateway/latest/userguide/storage-gateway-cached-concepts.html
0
0
Agree A.
Not B because:
In the gateway-stored volume solution, you maintain your volume storage on-premises in your data center. That is, you store all your application data on your on-premises storage hardware.
source: http://docs.aws.amazon.com/storagegateway/latest/userguide/storage-gateway-stored-volume-concepts.html
1
0
Customer wants off site BACKUP with low latency access to data
Gateway-stored volumes let you store your primary data locally, while asynchronously backing up that data to AWS. Gateway-stored volumes provide your on-premises applications with low-latency access to their entire datasets, while providing durable, off-site backups
So to me B is correct – although its a pretty shit question.
0
0
It all backs up regardless of gateway stored or cached. The questions states they want low latency for frequently accessed, not all, so it is gateway cached.
1
0
A = Since the requirement is “off-site backup of this data, while maintaining low-latency access”
0
0
A = Since the requirement is “off-site backup of this data, while maintaining low-latency access to their frequently accessed “
0
0
Not A because Gateway-Cached moves data out of on-prem so it is no longer the backup
0
0
Says also “snapshot”. There is your backup
0
0
from – https://aws.amazon.com/storagegateway/faqs/
Gateway-Stored Volumes: In the event you need low-latency access to your entire data set, you can configure your gateway to store your primary data locally, and asynchronously back up point-in-time snapshots of this data to Amazon S3. Gateway-Stored volumes provide durable and inexpensive off-site backups that you can recover locally or from Amazon EC2 if, for example, you need replacement capacity for disaster recovery.
still a really crap question and I still cant make up my mind if A or B yet….
0
0
Its not B for sure but can it be D, I am confused between A & D.
0
0
I choose D
0
0
A is the correct answer.
Gateway-cached volumes allow you to utilize Amazon S3 for your primary data, while retaining some portion of it locally in a cache for frequently accessed data. These volumes minimize the need to scale your on-premises storage infrastructure, while still providing your applications with low-latency access to their frequently accessed data. You can create up to 32 volumes up to 32 TB in size each, for a total of 1 PB of data capacity per gateway, and mount them as iSCSI devices from your on-premises application servers. Data written to these volumes is stored in Amazon S3, with only a cache of recently written and recently read data stored locally on your on-premises storage hardware.
You cant have more than 2.5TB with VTL
3
0
@fun4now
https://aws.amazon.com/storagegateway/faqs/
QHow much data can I store in a Virtual Tape Library?
Each Virtual Tape Library (VTL) can store up to 1,500 virtual tapes with a maximum aggregate capacity of 1 PB.
0
0
I would still think the answer is A because the requirement is with low latency
so I will go with A, please share your throughts
0
0
The Key in the question is “while maintaining low-latency access to their frequently accessed data”
The Answer is “A” – Gateway-Cached Volumes.
Gateway-cached volumes – You store your data in Amazon Simple Storage Service (Amazon S3) and retain a copy of frequently accessed data subsets locally. Gateway-cached volumes offer a substantial cost savings on primary storage and minimize the need to scale your storage on-premises. You also retain low-latency access to your frequently accessed data.
2
0
Another reason it’s A is it says “increasingly constrained with their local storage capacity”, indicating they don’t want to store everything locally.
0
0
Exactly!
0
0
I am going with A
0
0
A is correct answer.
1
0
A
0
0
I think this is an important aspect of the question – “This repository is growing at 500 GB a year and must be presented as a single logical volume”. Within six years, if the local Volume continues to be the primary source, it wont be able to present the data as a single logical volume
0
0
That rules out A
0
0
And B is also rule out, and you can rule out C and D based on the latency expected of VTL. As mentioned before, unfair question
0
0
Gateway-cached volumes let you use Amazon Simple Storage Service (Amazon S3) as your primary data storage while retaining frequently accessed data locally in your storage gateway. Gateway-cached volumes minimize the need to scale your on-premises storage infrastructure, while still providing your applications with low-latency access to their frequently accessed data.
>>> that means S3 will be primary storage while customer still keep accessing to existing local storage, and the increase of local storage will be minimized
>>> A is correct
0
0
A
They said they are increasingly constrained on local storage and want to maintain low latency to “frequently accessed files” <–That equals cached.
0
0
A
The question mentions they want low-latency access to their data. So that immediately rules out C and D.
The question also mentions they are constrained on local storage. Gateway store would still use local storage for all of the volumes it presents, which does not solve that problem, so B is out. Gateway cache uses S3 storage for the bulk of the data, while using a small slice of local data for a local cache. The cache works especially well for data that is accessed often, which also matches the question hint about “frequently accessed data”. Definitely A.
0
0
But doesnt option A void this requirement:
‘wants an off-site backup of’
Off-site would be the data set with Cached, not the backup. Gateway-Volumes would meet the backup requirement at least
0
0
I will go with A. Since company need “low latency” access to “frequently” access data that is provided by Cached volumes as per below
http://docs.aws.amazon.com/storagegateway/latest/userguide/WhatIsStorageGateway.html
Volume Gateway – Volume Gateway provides cloud-backed storage volumes that you can mount as Internet Small Computer System Interface (iSCSI) devices from your on-premises application servers. The gateway supports the following volume configurations:
Cached volumes – You store your data in Amazon Simple Storage Service (Amazon S3) and retain a copy of “frequently accessed data subsets” locally. cached volumes offer a substantial cost savings on primary storage and minimize the need to scale your storage on-premises. You also retain low-latency access to your frequently accessed data.
Stored volumes – If you need low-latency access to your entire data set, you can configure your on-premises gateway to store all your data locally and then asynchronously back up point-in-time snapshots of this data to Amazon S3. This configuration provides durable and inexpensive off-site backups that you can recover to your local data center or Amazon EC2. For example, if you need replacement capacity for disaster recovery, you can recover the backups to Amazon EC2.
0
0
D is the best option here
Q: What is tape gateway?
Tape gateway presents your backup application with a virtual tape library (VTL) interface, consisting of a media changer and tape drives. You can create virtual tapes in your virtual tape library using the AWS Management Console. Your backup application can read data from or write data to virtual tapes by mounting them to virtual tape drives using the virtual media changer. Virtual tapes are discovered by your backup application using its standard media inventory procedure. Virtual tapes are available for immediate access and are backed by Amazon S3.
0
0
I confuse A and B
Perhaps A is right
The keywords are low latency for frequent data accessing, and constrain local data size.
Store Cache: Data will house on S3, and frequently data accessing will be kept in local.
0
0
A
0
0
As per AWS S3 WhitePaper
With gateway-cached volumes, you can use Amazon S3 to hold your primary data, while retaining some portion of it locally in a cache for frequently accessed data. Gateway-cached volumes minimize the need to scale your on-premises storage infrastructure while still providing your applications with low-latency access to their frequently accessed data. You can create storage volumes up to 32 TB in size and mount them as iSCSI devices from your on-premises application servers. Each gateway configured for gateway-cached volumes can support up to 20 volumes and total volume storage of 150 TiB. Data written to these volumes is stored in Amazon S3, with only a cache of recently written and recently read data stored locally on your on-premises storage hardware.
So A is the Answer
0
0
Answer = B
http://docs.aws.amazon.com/storagegateway/latest/userguide/WhatIsStorageGateway.html
0
0
B Will be correct Answer.
Kindly read the questions again.
0
0
B since it is frequently accessed.
0
0
Really interesting question and both A&B can be used, but as for me there is one primary reason why I choose B is off-site backup.
“Volume gateway provides an iSCSI target, which enables you to create volumes and mount them as iSCSI devices from your on-premises application servers. The volume gateway runs in either a cached or stored mode.
– In the cached mode, your primary data is written to S3, while you retain some portion of it locally in a cache for frequently accessed data.
– In the stored mode, your primary data is stored locally and your entire dataset is available for low-latency access while asynchronously backed up to AWS.”
https://aws.amazon.com/storagegateway/faqs/
I know there are words for A “with snapshots scheduled TO Amazon S3”, I think it should be “with snapshots scheduled ON Amazon S3”.
0
0
guys…
please google “Gateway-Cached volumes”, can we find anything? There’s only “Gateway-Stored volumes”
0
0
yes we can find a lot for “Gateway-cached Volumes” http://lmgtfy.com/?q=%22Gateway-Cached+volumes%22
0
0
from JM’s link, B is the answer. Talks about low latency and they want the volume as a single logical unit. In gateway-cached,z you have the entire volume in the cloud and a copy of frequently accessed data on-premise. So that does not fit this purpose. In gateway-stored, you have entire volume on-premise and have asynchronous backup to the cloud , and it also improves latency. B is correct
Cached Volumes – You store your data in Amazon Simple Storage Service (Amazon S3) and retain a copy of frequently accessed data subsets locally. Cached volumes offer a substantial cost savings on primary storage and minimize the need to scale your storage on-premises. You also retain low-latency access to your frequently accessed data.
Stored Volumes – If you need low-latency access to your entire data set, you can configure your on-premises gateway to store all your data locally and then asynchronously back up point-in-time snapshots of this data to Amazon S3. This configuration provides durable and inexpensive off-site backups that you can recover to your local data center or Amazon EC2. For example, if you need replacement capacity for disaster recovery, you can recover the backups to Amazon EC2.
0
0
its A, just read it again.
0
0
http://docs.aws.amazon.com/storagegateway/latest/userguide/WhatIsStorageGateway.html
Cached Volumes – You store your data in Amazon Simple Storage Service (Amazon S3) and retain a copy of frequently accessed data subsets locally. Cached volumes offer a substantial cost savings on primary storage and minimize the need to scale your storage on-premises. You also retain low-latency access to your frequently accessed data.
0
0