Licensing for Integration with Veeam Backup for AWS
When you add a Veeam Backup for AWS appliance to the Veeam Backup & Replication infrastructure, there are two possible scenarios:
- Connecting to an existing Veeam Backup for AWS appliance
- Deploying a new Veeam Backup for AWS appliance
Connecting to an Existing Veeam Backup for AWS Appliance
If you connect to an existing Veeam Backup for AWS appliance, the Paid or BYOL license installed on the Veeam Backup for AWS appliance becomes invalid. Protected EC2 instances start consuming instance units from the Veeam Backup & Replication license.
An EC2 instance is considered protected if it has a backup or snapshot created by a backup policy in the last 31 days. Each protected EC2 instance consumes 1 license unit. Note that the manual creation of EC2 snapshots does not require license units.
If you remove the Veeam Backup for AWS appliance from Veeam Backup & Replication infrastructure, Veeam Backup & Replication will stop counting backed-up EC2 instances. Veeam Backup for AWS continues using the license that was used before you added Veeam Backup for AWS to the Veeam Backup & Replication infrastructure.
Deploying a New Veeam Backup for AWS Appliance
If you deploy a new Veeam Backup for AWS appliance in the Veeam Backup & Replication console, protected EC2 instances start consuming instance units from the Veeam Backup & Replication license.
An EC2 instance is considered protected if it has a restore point created by a backup policy in the last 31 days. Each protected EC2 instance consumes 1 license unit. Note that creating cloud-native snapshots of EC2 instances does not consume license units.
If you remove the Veeam Backup for AWS appliance from Veeam Backup & Replication infrastructure, Veeam Backup & Replication stops counting backed-up EC2 instances. To continue using Veeam Backup for AWS, you will have to install a BYOL license on the Veeam Backup for AWS appliance. For details, see the Licensing section in the Veeam Backup for AWS User Guide.
Related Topics