5.3 Customer creation and backup resources

Once the Cloud Connect infrastructure is completely configured, license is in place, and hardware plans have been created (for replica services) a service provider can start to configure users and accept their incoming backups or replicas.

In the Cloud Connect node, select Add Tenant to start the customer creation wizard.

Create a new tenant

5.7: Create a new tenant

A tenant can be a Standalone account which uses the local Cloud Connect database to store credentials, or a vCloud Director account which uses existing vCloud Director organizations as Cloud Connect accounts. There’s also an option to use Active Directory to manage accounts, but this is mostly a solution for Enterprise customers using Cloud Connect, so we will not discuss this option in this book.

NOTE: vCloud Director accounts can be used also to offer backup services.

Standalone accounts

Standalone accounts need to be created locally into Veeam Cloud Connect. A username and a password needs to be configured (manually or automatically generated), and a lease time can optionally be configured, for example for trial purposes:

Create a new Standalone tenant

5.8: Create a new Standalone tenant

A customer of the service provider is uniquely identified as a tenant, and thus it can rent both backup and replication resources, and connect to them with the same credentials. For this reason, both options are grouped in the same section of the configuration process. In this first step, we are configuring backup resources; later we will also assign replication resources to the same tenant.

Then, limits can be configured for the tenant:

Specify connection limits

5.9: Specify connection limits

We described in details how concurrent tasks limits work in Veeam Cloud Connect in chapter 2.7, please refer to this chapter.

Bandwidth is an optional parameter that can be applied to a tenant, and it will limit the amount of traffic the tenant can generate. The bandwidth available to one tenant is equally split between all tasks performed by this tenant.

Gateway pools are also configured here:

Specify gateway pools

5.10: Specify gateway pools

Please refer to chapter 3.5 for additional details.

In the following step, at least one Cloud Repository needs to be configured. A user can have multiple cloud repositories, for example with or without WAN acceleration, or stored on Backup Repositories with different characteristics and price per GB:

Configure a new Cloud Repository

5.11: Configure a new Cloud Repository

The Cloud Repository is created and assigned to the tenant:

Tenant list of backup resources

5.12: Tenant list of backup resources

In the backup resources step the service provider can also configure Insider Protection, as explained in details in chapter 3.8.

The service provider completes the wizard, and the tenant is ready to consume the assigned backup resources.

At any point in time, the service provider can edit the tenant configuration, and modify any parameter.

vCloud Director accounts

If vCloud Director is used, service providers can use its users to authenticate and authorize Veeam Cloud Connect tenants, for both backup and replication services.

vCloud Director tenant creation

5.13: vCloud Director tenant creation

In this case, the new tenant is not created, rather is selected among the existing vCloud Organizations:

Select vCloud Organization

5.14: Select vCloud Organization

The following steps are the same as for Standalone accounts. We will see more differences in the following chapters, when talking about replication resources.