AWS Storage Gateway Integration for MSP Bank: Achieve Seamless On-Premises and Cloud Data Security and Storage

AWS Storage Gateway Integration

Question

MSP Bank, Limited is a leading Japanese monetary institution that provides a full range of financial products and services to both institutional and individual customers.

It is headquartered in Tokyo.

MSP Bank is hosting their existing infrastructure on premise. MSP bank has lot of web applications, databases and data warehouse built on Teradata, NoSQL databases, and other types of data stores.

MSP bank has lot of data assets in terms of logs, documents; excel files, CSV files, PDF documents and others.

MSP Bank wants to provide seamless integration with data security features between their on-premises IT environment and the AWS storage infrastructure.

MSP bank considers AWS Storage Gateway to address the integration. MSP Bank is looking at gateway interface which provides cloud-backed storage volumes that you can mount as Internet Small Computer System Interface (iSCSI) devices from your on-premises application servers.

Also need low-latency access to your entire dataset thereby configuring on- premises gateway to store all your data locally, then asynchronously back up point-in-time snapshots of this data to Amazon S3? How can this be achieved? select 2 options.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Answer: A,C.

Option A is correct -A 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 retainlow-latency access to your frequently accessed data.

Stored volumes - If you need low-latency access to your entire dataset, first configure your on-premises gateway to store all your data locally.

Then asynchronously back up point-in- time snapshots of this data to Amazon S3

This configuration provides durable and inexpensive offsite 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

https://docs.aws.amazon.com/storagegateway/latest/userguide/WhatIsStorageGateway.html

Option B is incorrect -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.

https://docs.aws.amazon.com/storagegateway/latest/userguide/WhatIsStorageGateway.html

Option C is correct -Stored volumes - If you need low-latency access to your entire dataset, first configure your on-premises gateway to store all your data locally.

Then asynchronously back up point-in- time snapshots of this data to Amazon S3

This configuration provides durable and inexpensive offsite 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

https://docs.aws.amazon.com/storagegateway/latest/userguide/WhatIsStorageGateway.html

Option D is incorrect -With a tape gateway, cost-effectively and durably archive backup data in Glacier.

A tape gateway provides a virtual tape infrastructure that scales seamlessly with your business needs and eliminates the operational burden of provisioning, scaling, and maintaining a physical tape infrastructure.

https://docs.aws.amazon.com/storagegateway/latest/userguide/WhatIsStorageGateway.html

MSP Bank wants to provide seamless integration with data security features between their on-premises IT environment and the AWS storage infrastructure. To achieve this, MSP Bank is looking at the gateway interface that provides cloud-backed storage volumes that can be mounted as iSCSI devices from on-premises application servers. Additionally, they need low-latency access to their entire dataset, and the ability to configure on-premises gateway to store all their data locally, and then asynchronously back up point-in-time snapshots of this data to Amazon S3.

There are three types of AWS Storage Gateway that can be used to achieve these requirements: Volume Gateway, Cached Volumes, and Stored Volumes. Tape Gateway is not suitable in this scenario as it is used for backup and archive purposes only.

  1. Volume Gateway: Volume Gateway provides cloud-backed storage volumes that can be mounted as iSCSI devices from on-premises application servers. There are two types of volume gateway: Stored Volumes and Cached Volumes.
  • Stored Volumes: Stored Volumes provide on-premises applications with low-latency access to their entire data set. The data is stored locally on the gateway, and asynchronously backed up to Amazon S3. In this scenario, MSP Bank can configure their on-premises gateway to store all their data locally, then asynchronously back up point-in-time snapshots of this data to Amazon S3. This option fulfills both the requirements of seamless integration with data security features between their on-premises IT environment and the AWS storage infrastructure and low-latency access to their entire data set.

  • Cached Volumes: Cached Volumes provide a cache of frequently accessed data in the gateway, with the rest of the data stored directly in Amazon S3. This option is suitable for scenarios where only a subset of the data set is frequently accessed, and low-latency access is not required for the entire data set.

  1. Cached Volumes: Cached Volumes provide a cache of frequently accessed data in the gateway, with the rest of the data stored directly in Amazon S3. This option is suitable for scenarios where only a subset of the data set is frequently accessed, and low-latency access is not required for the entire data set.

In conclusion, the two options that can be used to achieve MSP Bank's requirements are:

  1. Stored Volumes
  2. Cached Volumes.

Stored Volumes provide low-latency access to the entire data set while asynchronously backing up point-in-time snapshots of the data to Amazon S3, making it suitable for MSP Bank's requirements. Cached Volumes are suitable for scenarios where only a subset of the data set is frequently accessed, and low-latency access is not required for the entire data set.