Veeam Backup for AWS Private Network Deployment Automation
Purpose
This article provides information about Veeam Backup for AWS support for private deployment mode. It will explain how to use the attached script to configure network settings for buckets (used as repositories) and workers (used for backups).
To learn more about implementing Private Deployment Mode, review the Enabling Private Network Deployment section of the Veeam Backup for AWS User Guide.
Solution
Package Contents
The download package contains five files:
- 00 Bucket.json — CloudFormation details for configuring buckets
- 10 Worker.json — CloudFormation details for configuring workers in all regions
- 15 Vb.json — CloudFormation details for configuring the Veeam Backup server
- 20 BucketRoute.json — CloudFormation details for configuring buckets routing
- deploy.sh — Script to perform the actual deployment
No changes to the files are necessary to make them work, simply pass the expected arguments to the deploy.sh and it will handle the rest.
However, if required, the naming of tag values and other details can be changed to your liking.
Functionality
This script will allow you to deploy VPCs with all required settings for:
- Veeam Backup appliance (configured with two subnets: public and private NAT gateways)
- Workers (you will have to specify all regions you’re going to work with as parameters within deploy.sh)
- Bucket
Deploy.sh Argument Requirements
When executing the deploy.sh script, two sets of parameters have particular requirements that you must ensure you accommodate:
- The worker_regions and worker_cidrs parameters:
- They must be a list of values separated by a comma (without any spaces).
- The number of worker_regions and workers_cidrs specified must match (e.g., if you specify three worker regions, there must be three worker cidrs).
- The order of the values specified for worker_regions and worker_cidrs must match (i.e., the first worker_region specified must match the first worker_cidrs value specified, and so on).
- The vb_public_cidr and vb_private_cidr values must be a subset of the vb_cidr value. The public and private cidr values must not overlap each other.
Example of Script Execution
The deploy.sh script processes eight arguments during its execution, which may be passed using an easier-to-read multi-line input format or all in one line.
Example Explanation
In the examples below, the script will perform the following tasks:
- Configure a bucket in ap-southeast-2 (Asia Pacific (Sydney))
- Configure workers to be able to run in ap-northeast-1 (Asia Pacific (Tokyo)) and ap-southeast-2 (Asia Pacific (Sydney))
- Prepare ap-southeast-2 (Asia Pacific (Sydney)) for running the Veeam Backup server
Method 1: Multi-Line Input of Arguments (Easier to Read)
Note that each line is executed sequentially, assigning values to variables and then excuting the deploy.sh command using those variables.
Method 2: One-Line Argument Input
In this method, each argument the deployed.sh script would expect is provided on the same line as the deploy.sh.
Example formatting:
bash deploy.sh "ap-southeast-2" "10.0.0.0/16" "ap-northeast-1,ap-southeast-2" "10.2.0.0/16,10.3.0.0/16" "ap-southeast-2" "10.10.0.0/16" "10.10.1.0/24" "10.10.2.0/24"
Download Information
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.