#VEEAM BACKUP TO AWS WINDOWS#
Create Separate windows virtual machines for Backup Server, you can refer the installation from our blog or refer to Installing Veeam Backup & Replication guide. Setting Up Backup Environmentįirst, we need to deploy Veeam Backup and Replication (B&R) servers in VMC as Virtual Machines. You can configure multiple Linux Repository based on the IOPS requirement using different EBS volume types available in AWS like SSD (GP2), HDD ( ST1) etc. This will help for efficient data transfer over the fast ENI connection used by VMware to communicate with AWS. Amazon EC2 Linux instance can be used as a repository server and launched from the connected VPC. Backup Repository:As per the best practice it is recommended to use a backup repository created outside of the VMware Cloud on AWS environment.To provide enough resources for the smooth backup operation, deploy at least one backup proxy on the SDDC cluster which is required for AWS specific Hot-Add processing in the VMware Cloud on AWS. You can assign the role of the backup proxy to a dedicated VM or to the backup server. Backup Proxy: Backup proxy will be deployed as Windows 2016 or 2019 virtual machine in the in the VMware Cloud on AWS environment.Backup Server: Veeam backup server will be deployed as Windows 2016 or 2019 virtual machine in the VMware Cloud on AWS environment.
#VEEAM BACKUP TO AWS INSTALL#
Per this deployment type, you can install the backup server and the backup proxy on the same VM. Simple deployment is preferable for VMware Cloud on AWS environments with low traffic load. In this post, we will cover the simple deployment method of protecting VMC ON AWS workloads using Veeam Backup & Replication.
As I mentioned in the previous post there are two types of deployments available one is simple deployment, and another is advanced. In the previous blog post, we have given a brief about protecting the VMC ON AWS workloads using Veeam Backup & Replication.