Ok so at this stage we can right click on the machine we wish to directly restore to AWS. You will then see your newly added cloud credentials. Notice how I am not going to show you my secret key. We can choose to add our Amazon AWS Access Key from the selection.įrom your Amazon account you will need to provide your Access Key and Secret Key these are super super important not to share externally.
We are now in a position where we can see the contents of the backup, and from here we can begin our tests.įor us to test the direct restore to AWS functionality then we first need to add our AWS Cloud Credentials. Next you will see the progress, this should not take long. If the backup file also contains guest file system index, then you can check the box to import this also.
#Veeam backup for aws full#
We can choose different Veeam files I changed the file type to VBK so I could see the full backup file in the directory. It’s really simple to import any Veeam backup first up open up the Veeam Backup & Replication console and connect to the Veeam Backup & Replication server, if using the console on the server then you can choose “localhost”ĭepending on where that backup file is located you will need to select this from the drop down, if this is not on an already managed Veeam server (i.e separate to the the Veeam backup & replication server, you will need to add this) Next up we need to import this to our AWS Veeam Backup & Replication server. this is located within the repository in AWS.
#Veeam backup for aws free#
On this machine we then installed Veeam backup & Replication – Community Edition, the functionality of cloud mobility is completely available within the free community edition.Īs you can see in the below image, we have a full backup file.
#Veeam backup for aws windows#
This Veeam Backup & Replication server within AWS is a Windows 2016 machine with the following specifications. We then have a complete stand-alone system running within AWS that has Veeam Community Edition installed.
We are then for the purposes of the test going to backup copy those backups to a secondary backup repository to a machine running in AWS. I wanted to check and compare the speed and performance of this but also if we did see a dramatic increase in speed then at what cost does this come at.Īs you can see from the diagram above, we have our production environment on the left and this is the control layer for the operational backups for our production workloads. A couple of weeks back at Cloud Field Day one of the questions asked by the delegates was would the conversion process for the Direct Restore to AWS be faster if we stored the data within AWS as part of the backup process, for example if we were to have our on-premises operational restore window local to the production data but have a backup copy job sending a retention period to a completely separate Veeam Backup & Replication server and repository that is located within AWS.