Greetings friends, the first strong post of September, today I bring you a very entertaining post about Veeam Backup and Replication on a Repository based on AWS Storage Gateway, and as it has stayed a little long I want to leave here the menu to move you faster:
- AWS Storage Gateway – quick overview
- Deploying the AWS Storage Gateway Virtual Appliance on vSphere
- Configuring AWS Storage Gateway
- How to create a File Share on Amazon S3
- How to create a Repository on Veeam Backup and Replication
- Backup Copy job – quick overview
- Backup job – quick overview
- How to monitoring with Cloud Watch
Note: This procedure is not officially supported by Veeam, and it will only work as expected if the Storage Gateway is properly sized, in terms of disk, RAM/CPU, and fastest disk. More information on the official Helpcenter Information link.
AWS Storage Gateway – quick overview
AWS Storage Gateway allows us to consume certain Amazon Web Services resources locally through a virtual appliance that we deploy in our Infrastructure, so our VMs view the resources as if they were local, while the information is replicated in an encrypted and compressed way to the Amazon Cloud.
- File Share: Which is nothing more or less than an NFS where we can connect computers that will see a traditional network drive and store files there.
- Volumes: Where we can consume by iSCSI, volumes that we can connect to Windows, Linux, etc., and that will be replicated later.
- Tapes: Virtual tape drives with which we can launch backups with Veeam for example, as if a real tape was involved, and thus get a more durable storage such as tapes, but in Cloud.
We can store the information in three different types of Amazon storage:
- Amazon S3, recommended for files or volumes that we use frequently.
- Amazon Glacier, if what we are saving is not accessed frequently.
- Amazon EBS Snapshots.
This is how our Veeam Backup and Replication Infrastructure with AWS Storage Gateway would look like.
Deploying the AWS Storage Gateway Virtual Appliance on vSphere
The first thing we’ll do is go to the AWS Storage Gateway website, select the region at the top right and press Get started.
Configuring AWS Storage Gateway
Back to the configuration, we will now enter the IP of the AWS Storage Gateway VM, and press Connect to gateway.
Now in our AWS Storage Gateway VM we will create the cache disks, we can create one or several, besides hosting them in the Datastore that we want, if we want better speed locate it in fast disk, if the speed is not a problem, then in SATA.
Keep in mind that the cache disk is used until the information is transferred, so you need to have enough space for our copies of the VMs.
If we want to configure the static IP within the AWS Storage Gateway or perform other operations, we will enter the VM console:
How to create a File Share on Amazon S3
Once we have the cache disk or disks ready, the next step is to create File Share, we can do it by pressing the button you see in the image:
Back to the AWS Storage Gateway wizard, we will select the gateway we have and manually enter the name of the S3 bucket we just created. We can select at this time if we want it to be S3 Glacier or S3 normal. I selected normal.
The next step will allow us to further configure and filter the appearance of the NFS server that will be configured in the AWS Storage Gateway we have locally. (It can be edited later, so don’t worry)
How to create a Repository on Veeam Backup and Replication
By offering only one NFS drive, we will use a Linux repository to access this NFS, in our Veeam we will go to the wizard to create a new repository:
In the path to folder we can edit if we want where the copies will be saved, but by default I have left backups in the folder. In addition we can always play a little bit with the advanced settings, simultaneous tasks, etc.En el path to folder podemos editar si queremos donde se guardaran las copias, pero por defecto he dejado en la carpeta backups. Además siempre podemos jugar un poco con las configuraciones avanzadas, tareas simultáneas, etc.
Backup Copy job – quick overview
Let’s run a test with a Backup Copy job, let’s go to the wizard and select VMware:
Backup job – quick overview
I do not extend myself in the configuration of a Veeam copy job, as it is the usual, here the result of a full copy of a VM to this new repository, it took only 23 minutes and 16GB have been transferred.
How to monitoring with Cloud Watch
It is very interesting to see with Cloud Watch the consumption of bandwidth, or disk writing, etc. For example, these are the statistics of File Share, we can see how many bytes we write when we make the backup copy job, how much with the backup job full and how much with the backup job in incremental. In addition, the thin purple line is the constant synchronization between the cache and Amazon S3, consuming about 1Mbps continuously.
This is all friends, in future posts we will see an AWS Storage Gateway tutorial with Volume by iSCSI and Virtual Tape Drive as well.
If you have any questions with Amazon AWS Storage Gateway scaling and Veeam I recommend you write to my friend James