By default, Veeam Backup & Replication encrypts data traffic going to and from the cloud repository. Additionally, tenants can encrypt backups created with backup jobs, backup copy and replication jobs. To do this, tenants must enable the data encryption option in the job properties.
Network Traffic Throttling
The SP can select to throttle traffic going to and from the cloud repository. Data throttling rules are specified in the same manner as for regular backup infrastructure components.
By default, the Veeam backup server shares available bandwidth equally between all tenants who work with cloud backup and replication resources simultaneously. The bandwidth available to one tenant is equally split between all tasks performed by this tenant.
For example, the cloud repository is used by two tenants simultaneously:
- Tenant 1 runs 2 tasks, backup and restore.
- Tenant 2 runs 1 task.
In this situation, Tenant 1 will get 50% of bandwidth and this bandwidth will be equally split between 2 tasks: 25% of the initial bandwidth per task. The task performed by Tenant 2 will get 50% of the initial bandwidth.
To adjust network bandwidth consumption individually for each tenant, the SP can specify the bandwidth limit when assigning cloud backup and replication resources to a tenant. In this case, tenant's backup and replication jobs will split the specified bandwidth regardless bandwidth consumption by other tenants.
Veeam Cloud Connect supports parallel data processing. The SP can specify the maximum number of concurrent tasks that can be performed within tenant jobs targeted at the cloud repository and cloud host. Task limitation settings are specified individually for each tenant at the process of the tenant account registration. To lean more, see Specify Bandwidth Settings.
When multiple concurrent tasks are allowed for the tenant, the tenant can process in parallel the corresponding number of VMs and/or VM disks within a single backup or replication job targeted at the cloud repository or cloud host. Parallel data processing also lets the tenant perform multiple jobs targeted at the cloud simultaneously.
For backup copy jobs targeted at the cloud repository, Veeam Backup & Replication allows to process multiple jobs or multiple VMs in the job in parallel. VM disks are always processed subsequently, one by one.
The maximum number of concurrent tasks specified for a tenant should not exceed the maximum number of concurrent tasks specified for backup proxies and backup repositories deployed by the SP as a part of the Veeam Cloud Connect infrastructure. Ignoring this rule can lead to overload of backup infrastructure components that take part in processing tenant data.
For example, the tenant has included 1 VM with 4 disks into a backup job targeted at the cloud repository. On the SP side, the following task limitation settings are specified:
- The tenant can process 4 concurrent tasks.
- The cloud repository can process 2 concurrent tasks.
In this situation, Veeam Backup & Replication on the tenant backup server will start 4 concurrent tasks. With only 2 concurrent tasks allowed on the cloud repository, Veeam Backup Service on the SP backup server will have to wait for available resources on the repository, thus impacting the backup job performance.
Resource limitation settings for backup proxies and backup repositories deployed as a part of the Veeam Cloud Connect infrastructure are specified in the same manner as for regular backup infrastructure components. To learn more, refer to the Veeam Backup & Replication User Guide at: https://www.veeam.com/documentation-guides-datasheets.html.
To use parallel data processing capabilities of Veeam Cloud Connect, both the SP and tenant must have the current version of Veeam Backup & Replication installed on the Veeam backup server. For tenants who use previous versions of Veeam Backup & Replication, VMs in jobs and tasks within a single job will be processed subsequently regardless of the number of concurrent tasks specified for the tenant on the SP side.