Considerations and Limitations

In this article

    When you plan to deploy and configure Veeam Backup for AWS, keep in mind the following limitations and considerations.

    Important

    Veeam Backup for AWS is available only in AWS Global and AWS GovCloud (US) regions.

    Licensing

    If the license file is not installed, Veeam Backup for AWS will operate in the Free edition allowing you to protect up to 10 instances free of charge.

    Hardware

    The minimum recommended EC2 instance type for the backup appliance is t2.medium. For the list of all existing instance types, see AWS Documentation.

    Software

    To access Veeam Backup for AWS, use Microsoft Edge (latest version), Mozilla Firefox (latest version) or Google Chrome (latest version). Internet Explorer is not supported.

    Security Certificates

    Veeam Backup for AWS supports certificates only in the .PFX and .P12 format.

    Backup Repositories

    Before you start managing backup repositories, consider the following:

    If you use a KMS key to encrypt a repository, do not disable or delete this key. Otherwise, Veeam Backup for AWS will not be able to encrypt and decrypt data stored in the repository.

    • Even though an Amazon S3 bucket is no longer used as a backup repository, Veeam Backup for AWS preserves all backup files previously stored in the repository and keeps these files in Amazon S3.

    If you no longer need the backed-up data, either delete it as described in sections Removing EC2 Backups and Snapshots and Removing VPC Configuration Backups before you remove the repository from the Veeam Backup for AWS infrastructure, or use the AWS Management Console to delete the data if the repository has already been removed.

    Backup

    Before you start protecting AWS resources, consider the following:

    • Veeam Backup for AWS protects only EC2 instances that run in VPCs. EC2-Classic instances are not supported. For more information, see this Veeam KB article.
    • When Veeam Backup for AWS backs up EC2 instances with IPv6 addresses assigned, it does not save the addresses. That is why when you restore these instances, IP addresses are assigned according to the settings specified in AWS for the subnet to which the restored instances will be connected.
    • Veeam Backup for AWS does not support backup of RDS instances running the Amazon Aurora relational database engine.
    • Veeam Backup for AWS supports backup of EFS file systems only to the same AWS accounts where the source file systems belong.
    • Veeam Backup for AWS does not support backup of the following VPC configuration components: VPC Traffic Mirroring, AWS Network Firewall, VPC Flow Logs, carrier gateways, customer IP pools, Gateway Load Balancers, Gateway Load Balancer endpoints and VPC endpoint services for Gateway Load Balancer endpoints.

    Restore

    Before you start restoring AWS resources, consider the following:

    • When restoring multiple EC2 instances that have the same EBS volume attached, Veeam Backup for AWS restores one volume per each instance and enables the Multi-Attach option for every restored volume. For more information on Amazon EBS Multi-Attach, see AWS Documentation.
    • Restore of files and folders is supported only for the following file systems: FAT, FAT32, NTFS, ext2, ext3, ext4, XFS, Btrfs.

    For EC2 instances running Microsoft Windows OSes, Veeam Backup for AWS supports file-level restore only for basic volumes.

    • Veeam Backup for AWS supports restore of EFS file systems only to the same AWS account where the source file systems belong.
    • Restore of entire VPC configurations to a new location is not supported for the following VPC configuration items: Client VPN endpoints, customer gateways and load balancer listeners that use authentication certificates and specific components of route tables (routes to AWS Outpost local gateways, network interfaces, instances and carrier gateways).
    • Restore of specific VPC configuration items to a new location is not supported.