Backup Appliance

You can choose the type of the EC2 instance running Veeam Backup for AWS during the deployment, or change it later as the environment grows.

General Recommendations

The following recommendations and examples apply to the latest Veeam Backup for AWS builds (7.0.0.615 or later).

When defining the instance type and amount of RAM required for proper functioning of the backup appliance, take into account the following:

• The average amount of RAM consumed in the idle state (approximately 1.5 GB).
• 5% of the total backup appliance RAM required for the Veeam Backup for AWS Web UI and REST API service.
• The maximum amount of RAM consumed by running backup policies. For more information, see Backup Policies.

The RAM consumed by a backup policy depends on the data protection scenario.

Note that these values are provided for demonstration purposes only. For production environments, it is recommended that you allocate an additional margin of 20% RAM.

RAM Sizing Examples

Consider the following example. You configure a number of backup policies to protect your workloads by regularly creating snapshots, snapshot replicas and backups. In this case, we advise to allocate minimum 150 MB per 1 policy.

The amount of RAM utilized by policies running on a backup appliance (Utilized RAM) depends on the total amount of RAM allocated to the backup appliance, the number of configured backup policies and the number of workloads protected by one policy. However, consider that the actual amount of RAM available for policy execution (Free RAM) will also be affected by the OS and Veeam services operation.

1The table shows the maximum amount of RAM utilization when all backup policies run at the same time.

2Additional RAM required for any other software must be calculated separately.

CPU Sizing Examples

*The examples apply only to workloads protected by snapshots and snapshot replicas, as the backup process is performed by worker instances.

Configuration Restore Recommendations

The following is recommended for large-scale deployments.

• The root EBS volume attached to the backup appliance must have at least twice as much free space as the size of the configuration backup file. If the backup file grows too large, you can increase the volume size as described in AWS Documentation. Alternatively, open a support case to remove the unnecessary data from the configuration database.
• The EBS volume where Veeam Backup for AWS stores its configuration database must have at least twice as much free space as the size of the database. During configuration restore, Veeam Backup for AWS first creates the restored database and then deletes the original one.

Logging Recommendations

You can modify the following logging options in the configuration file /etc/veeam/awsbackup/config.ini:

If the log files grow too large, you can remove them from the /mnt/vcb-storage/logs or /var/log/veeam folder, or open a support case to remove the unnecessary data.

Veeam Backup & Replication Integration

When you connect a backup appliance to the backup infrastructure, its backup policies, cloud-native snapshots, image-level backups, backup repositories and sessions are imported into the Veeam Backup & Replication database.

Time Consumption

When you connect an existing backup appliance to the backup infrastructure, the integration process includes the following steps:

• Retrieving data from the backup appliance.
• Saving the retrieved data to the Veeam Backup & Replication database.

*The results were obtained when testing the backup appliance (c5.4xlarge, 16-core CPU, 32 GB RAM), the Veeam Backup & Replication server (PGSQL, 16-core CPU, 16 GB RAM) and Veeam Backup & Replication server (MSSQL, 16-core CPU, 16 GB RAM) and are approximate.