This week I will explain Amazon Web Services Storage Gateway. Storage gateway is a basically a replication tool to use both on-promise and on AWS infrastructure. Common usage examples of storage gateway are backup, disaster recovery , file sharing and data replication. Two main storage gateway types are volume based and tape based. Before proceeding with the demo , I want to explain more details about them.
– Volume Gateways: As it named, we can create volumes and then mount them as standard volume on our operating systems using ISCSI ( I can say this is backup-to-disk option in traditional backup solutions). Volume gateways also have two types, gateway-cached and gateway-stored.
* Gateway-cached volumes: The most part of the data is kept on AWS S3( primary storage) and frequently accessed data is kept on local storage. We can use total 20 Volumes sizing between 1GiB to 32TB. To use gateway-cached volume , we have to provision storage on AWS ( to mount on servers ) , provision storage on-premise (both for cache storage and upload buffer). We can take snapshots of our volumes and mount them as EBS to our instances on AWS. By the way, cache storage is used for frequently accessed data and upload buffer is used for staging the data that will be replicated to AWS.
* Gateway-stored volumes: The data is kept local storage and asynchronously backed-up to AWS as snapshots. We can use total 12 Volumes sizing between 1GiB to 1TB. To use gateway-store volume , we have to provision storage on-promise ( to mount on servers ) , provision storage on-premise (for upload buffer). We can take snapshots of our volumes and mount them as EBS to our instances on AWS.
– Gateway-VTL : We can use this type as traditional backup-to-tape solutions. We create virtual tapes ( upto 1500 sizing between 100Gib to 2,5TB) and backup our data to AWS S3. We can also use virtual tape shelves and use AWS Glacier service for archiving. For detail use of Gateway-VTL visit this link.
Today I will configure Gateway-Cached volume and mount it to a Windows OS to use with Veeam backup.
Ok Let’s go.
First of all , We need to create a gateway using AWS console. On AWS consolei I click “Deploy a new Gateway” and select “Gateway-Cached volumes”.
I choose “I want to run the AWS Storage Gateway on VMware ESXi” since I am using ESX servers.
Now I need to download the OVA file and deploy it ot my esx server. I downloaded it and now I will deploy it. In Vmware console, I select the Ova file and proceed. The image provided by AWS has some requirements and you can learn them here.
After deployment, I need to provision disks for upload buffer and cache storage. I use the minimum required disk sizes for my demo. I will explain real calculations in my next posts. Also in wizard Step 2 of 2 (Allocate Disks to Cache Storage) , there is a calculator for this. The virtual machine time needs to be correct , otherwise the activation will fail.
Now ESX side is done and I start my vm. After it booted , I need it’s ip address to activate on AWS.
Now it’s time for configuring our gateway. The first step is configuring our local disks. After I select my gateway, on “Gateway” tab, I select “Configure Local Storage”. I choose my provisioned disk on ESX and assign them as upload buffer and cache storage.
Next I will configure my volume that will be mounted as backup disk. I select 500GB and use awsbackup as target name. I don’t use snapshot ID since I don’t create the voume using a snapshot (I will explain later how to use snapshots).
Let’s see the details of it. I didn’t use CHAP authentication. If you wan to enable it visit this link.
Ok it is time to mount the volume to our server. I use Windows iscsi initiator and configure iscsi settings. In “Discovery” tab, I can see my iscsi target. If I go to “Target” tab, I can see that it is inactive.
I make it online and initialize.
Then I create a new disk.
So we configured our cached volume and attached it to our server. I will continue to use this disk as backup destination for my Veeam software. On my next post, I will explain how to monitor the performance of our gateway and also how to add/increase the disks we use for upload buffer, cache storage and volume.
If you have any question or comment, please feel free to write and don’t forget to share please.