AWS Storage Gateway, Руководство пользователя

Страница: 15 / 438

AWS Storage Gateway User Guide
Pricing
AWS Storage Gateway Pricing
For current information about pricing, see Pricing on the AWS Storage Gateway details page.
Plan Your Storage Gateway Deployment
By using the AWS Storage Gateway software appliance, you can connect your existing on-premises
application infrastructure with scalable, cost-effective AWS cloud storage that provides data security
features.
To deploy Storage Gateway, you first need to decide on the following two things:
1. Your storage solution – Choose from one of the following storage solutions:
• File Gateway – You can use a file gateway to ingest files to Amazon S3 for use by object-based
workloads and for cost-effective storage for traditional backup applications. You can also use it to
tier on-premises file storage to S3. You can cost-effectively and durably store and retrieve your on-
premises objects in Amazon S3 using industry-standard file protocols.
• Volume Gateway – Using volume gateways, you can create storage volumes in the AWS Cloud.
Your on-premises applications can access these as Internet Small Computer System Interface (iSCSI)
targets. There are two options—cached and stored volumes.
With cached volumes, you store volume data in AWS, with a small portion of recently accessed data
in the cache on-premises. This approach enables low-latency access to your frequently accessed
dataset. It also provides seamless access to your entire dataset stored in AWS. By using cached
volumes, you can scale your storage resource without having to provision additional hardware.
With stored volumes, you store the entire set of volume data on-premises and store periodic point-
in-time backups (snapshots) in AWS. In this model, your on-premises storage is primary, delivering
low-latency access to your entire dataset. AWS storage is the backup that you can restore in the
event of a disaster in your data center.
For an architectural overview of volume gateways, see Cached Volumes Architecture (p. 3) and
Stored Volumes Architecture (p. 5) .
• Tape Gateway – If you are looking for a cost-effective, durable, long-term, offsite alternative for
data archiving, deploy a tape gateway. With its virtual tape library (VTL) interface, you can use
your existing tape-based backup software infrastructure to store data on virtual tape cartridges
that you create. For more information, see Supported Third-Party Backup Applications for a
Tape Gateway (p. 22) . When you archive tapes, you don't worry about managing tapes on
your premises and arranging shipments of tapes offsite. For an architectural overview, see Tape
Gateways (p. 6) .
2. Hosting option – You can run Storage Gateway either on-premises as a VM appliance, or as hardware
appliance or in AWS as an Amazon EC2 instance. For more information, see Requirements (p. 10) .
If your data center goes offline and you don't have an available host, you can deploy a gateway on an
EC2 instance. Storage Gateway provides an Amazon Machine Image (AMI) that contains the gateway
VM image.
Additionally, as you configure a host to deploy a gateway software appliance, you need to allocate
sufficient storage for the gateway VM.
Before you continue to the next step, make sure that you have done the following:
1. For a gateway deployed on-premises, you chose the type of host, VMware ESXi Hypervisor or
Microsoft Hyper-V. and set it up. For more information, see Requirements (p. 10) . If you deploy
API Version 2013-06-30
8