Greetings friends, we have already seen in the previous post that Veeam had launched Veeam Backup for AWS Free Edition, the solution to protect workloads on Amazon AWS without the need for agents. In addition, and as we all like, with a free version of up to 10 Instances. In addition, we have seen how to deploy it step by step, and its subsequent configuration as well, today we are going to see how to configure Veeam Backup & Replication to access the backups created by Veeam Backup for AWS and stored in S3.
If we look at the following diagram, we would be talking about points 5, 6, and 7:
Installing the Cloud Patch for Veeam Backup & Replication v9.5 U4
Before continuing, we will have to install the Cloud Patch for our Veeam Backup & Replication, so that we can see the S3 repositories where we have backups created by Veeam Backup for AWS, is very simple, we will go to this KB and download the patch:
The installer is a following that I’m not going to document 🙂 make sure you have the Backup Copy Jobs stopped, as well as the Replicas, install and start the product again.
Once installed the Cloud Patch for Veeam Backup & Replication v9.5 U4, we will have the Build 2866, make sure it is correct in your case:
Add a Veeam Backup for AWS External Repository in Veeam Backup & Replication v9.5 U4 (Cloud Patch)
Since we have everything ready, we will go to Backup Infrastructure – External Repositories – Add External Repository:
We will introduce a descriptive name for this new External Repository, in my case as you see, I have added a description that helps me to understand what I’m doing: 
We will introduce some AWS credentials with access to the S3 bucket where we have sent copies of Veeam Backup for AWS:
We will select the Datacenter region where this bucket is, besides selecting the bucket, and the folder where we have sent the backup, as previously (in Veeam Backup for AWS) I said that I wanted to encrypt the backups, I will have to use the password to decrypt them:
Restore information from backups found in External Repository
Already with the External Repository, we can go to Home, and in the section called Backups – External, we can see the working copies, with the EC2 icon, and from there we can restore files, restore this backup as an instance of EC2 or as Azure Instance:
Create Backup Copies to copy Backups from the External Repository to a Repo on-prem
Now that we have everything created, one of the options I like the most is to be able to create a backup copy from the S3 repository to our datacenter, we will create a new Backup Copy Job:
Select the instance or Backup Job of Veeam Backup for AWS:
Select where we want to store it locally, with GFS if we need weekly, monthly, etc: 
And we can see the work as a copy from S3 to our repository:
Restore information from backups of Veeam Backup for AWS that we have on-prem
Now with our local copies, we can see the working copies, with the EC2 icon, and from there we can restore files, restore this backup as an instance of EC2 or as Azure Instance, or even restore to VMware or Hyper-V:
For example, here I’m restoring the disk as VMDK to an ESXi host: It’s all friends, we’ve seen the full circle of workload protection in AWS EC2, make snapshots and Backups to S3, and use this S3 repository to restore or copy backups to our datacenter, from which we can convert that instance to a VM over VMware or Hyper-V, WOW!
As Veeam Backup for AWS is a very complete new product, I have prepared a series of blogs about the product, I hope you like them:
Leave a Reply