Step 6. Allocate Cloud Backup Resources

At the Backup Resources step of the wizard, you can allocate cloud repository resources to the company. A company to which cloud repository resources are allocated will be able to store in the cloud backups created with Veeam Backup & Replication and Veeam backup agents.

Provisioning of cloud repository resources requires a license that covers storing backups in the cloud. For details, see Licensing.

To allocate cloud repository resources for the company, configure a cloud repository:

1. Click Add.
2. In the Cloud repository name field, specify a friendly name of a cloud repository.
3. From the Backup repository list, select an underlying backup repository on the Veeam Cloud Connect server.
4. In the Quota field, specify the amount of space that you want to allocate to the company on the selected backup repository.
5. Select the Set unlimited quota check box if you want to allow the company to store an unlimited number of VMs and computers in the cloud repository.
6. To define the number of VMs and computers for the cloud repository:

1. Make sure the Set unlimited quota check box is cleared.
2. In the VMs quota field, specify the maximum number of VMs that the company is allowed to store on the cloud repository.

The VMs quota is a soft quota and puts no physical restriction on the cloud repository. When the company reaches the specified quota, Veeam Availability Console triggers the VMs stored in cloud repository alarm. You can customize this alarm in accordance with your requirements. For details, see Modifying Alarm Settings.

Company users will see this quota on the Cloud Backup Quota dashboard. For details, see Summary.

3. In the Workstations quota field, specify the maximum number of Veeam backup agents in the Workstation mode that the company is allowed to store on the cloud repository.

The Workstations quota is a soft quota and puts no physical restriction on the cloud repository. When the company reaches the specified quota, Veeam Availability Console triggers the Workstation agent backups stored in cloud repository alarm. You can customize this alarm in accordance with your requirements. For details, see Modifying Alarm Settings.

Company users will see this quota on the Cloud Backup Quota dashboard. For details, see Summary.

4. In the Servers quota field, specify the maximum number of Veeam backup agents in the Server mode that the company is allowed to store on the cloud repository.

The Servers quota is a soft quota and puts no physical restriction on the cloud repository. When the company reaches the specified quota, Veeam Availability Console triggers the Server agent backups stored in cloud repository alarm. You can customize this alarm in accordance with your requirements. For details, see Modifying Alarm Settings.

Company users will see this quota on the Cloud Backup Quota dashboard. For details, see Summary. 

7. If the client plans to use WAN accelerators for backup copy jobs that write data to the cloud, select the Enable WAN acceleration through the following WAN accelerator check box and choose a target WAN accelerator configured on the service provider side.

The source WAN accelerator must be configured on the company side. The company must select the source WAN accelerator when configuring a backup copy job.

8. Click OK.

You can add more than one cloud repository for the company. Repeat steps 1-8 for all cloud repositories you want to create.

9. To enable additional protection for company backup files stored on cloud repositories, select the Protect deleted backup files for N days check box and specify how long deleted backup files must be kept in the recycle bin on the Veeam Cloud Connect server.

With this option enabled, when a company deletes a backup from the cloud repository, Veeam Cloud Connect does not immediately delete the actual backup files. Instead, Veeam Cloud Connect removes the backup from the tenant Veeam Backup & Replication console and database and moves backup files to the "recycle bin" — a dedicated folder on the service provider storage.

This functionality protects companies from both straightforward deletion of all backups from the Veeam console, as well more sophisticated attack via reducing the job retention policy and running a few incremental backups on already encrypted production servers to push the production data out of the off-site backup chain.

For details on protection of deleted backups, see Insider Protection.