Link Search Menu Expand Document

Appliance

The backup appliance orchestrates snapshot, replica and backup operations. This is where you configure credentials, worker settings, backup repositories, policies, and can manage restore operations. As a control plane, several of the actual tasks are performed with workers. The appliance communicates with workers to perform the required tasks such as backup, restore, archive and retention operations.

Recommendations

If you want to change the appliance size you can change it during the deployment, however it is possible to change it after the deployment in case the environment grows.

The following recommendations and examples apply to the latest VBA builds 1.

Appliance size Advised number of workloads
T3.medium (default - 2 vCPU, 4 GiB RAM) 1-1000
T3.2xlarge (medium - 8 vCPU, 32 GiB RAM) 1000-3000
C5.9xlarge (large - 36 vCPU, 72 GiB RAM) 3000-5000

In order to properly function, there are 3 parameters that define the appliance size (and more important, the amount of memory required).

  • OS utilization: the average value of memory needed in idle state which is around 1.5GiB
  • VBA utilization: 5% of the total appliance memory required for VBA application (Web UI and REST API)
  • Policies utilization: memory used per running policy (200MiB per policy and 3 MiB per additional workload in the policy). For more information on policy maximums, see the policies page

By combining all the above, the appliance size can be defined using the formula below which will calculate how much memory is required to operate.

OS utilization + VBA utilization + policies utilization

The below table contains some examples regarding the sizing of the appliance. The following applies to the table.

  • Working space: amount of memory free after calculation of the amount required for the operating system and VBA application
  • Workloads in policy: amount of workloads per policy
  • Number of policies: amount of policies you can run within the working space (recommended)
  • Memory consumed by all policies: total memory consumed by running all policies at the same time

The numbers of policies is calculated by taking the amount of available working space and converting it to MiB (multiply by 1024). Once this number is calculated, divide it by the amount of memory required per policy (200MiB + (3MiB * number of workloads in the policy)).

Sizing examples

Total appliance memory Working space Workloads in policy Number of policies Memory consumed by all policies Free memory
4 GiB 4 GiB
- 1.5 GiB
- 4 GiB * 0.05 =
2.3 GiB
50 (2.3 * 1024)
/ (200 + (3 * 50)) =
7
(200 * 7)
+ (3 * 50)
= ~1.6 GiB
Around 300 MiB
16 GiB 16 GiB
- 1.5 GiB
- 16 GiB * 0.05 =
13.7 GiB
50 (13.7 * 1024)
/ (200 + (3 * 50)) =
40
(200 * 40)
+ (3 * 50)
= ~8.1 GiB
Around 5 GiB

The main aspect of which will define how much memory you require for the appliance is how many workloads you want to configure within a specific policy.

NOTE: The above information is only related to the OS, Veeam services and assurance to operate without issues. It does not take into calculations any additional software that may needs to be installed by company policies.

VBR integration

When integrating VBA with VBR, policy and retention data is imported into the VBR database.

You can connect more than one VBA appliance to a single VBR server, however make sure you size your VBR infrastructure appropriately. If working on a cross-geography cloud project it makes sense to use a VBR server per macro-region, to alleviate issues relating to latency as well and help with meet potential data residency regulations.

  1. Veeam Backup for AWS 5.0.0.452 or higher 


Back to top

Copyright © 2022 Solutions Architects, Veeam Software.