5.4 Backup and backup copy jobs

Once a customer has subscribed to Veeam Cloud Connect backup resources, he can start immediately to consume them.

In the Veeam Backup & Replication installation at the customer site, the customer goes into the Backup Infrastructure node, Service Providers sub-node, and select to add a new Service Provider:

5.15: Add a service provider

In the first step, the customer inputs the DNS name configured with Round Robin by the Service Provider. Unless the TCP port has been changed by the Service Provider, no additional configuration is needed at this step:

5.16: Configure server provider dns name and tcp port

By hitting the Next button, Veeam Backup & Replication at the tenant side connects to one of the Cloud Gateways based on the information retrieved from DNS, and checks the SSL certificate:

5.17: SSL certificate is verified upon connecting to Veeam Cloud Connect

As explained in more details in chapter 8.1, the certificate is issued by a recognized Certification Authority, so no security warning is raised. In the same step of the wizard, the customer will add the username and password created for him by the Service Provider.

By hitting Next again, Veeam Backup & Replication logs into the Cloud Connect infrastructure with the given credentials, and Cloud Connect returns the resources the tenant is entitled to consume:

5.18: VBR lists the resources a tenant is entitled to consume

When the customer completes the wizard, the service provider is registered in the corresponding section, and even more important the Cloud Repository is registered under the available backup repositories of the tenant and can be used as a target for backup and backup copy jobs:

5.19: Cloud repository is registered and ready to be used

A backup or a backup copy job is then configured in the same exact way, regardless the final destination is a local repository on the tenant’s premises, or a cloud repository exposed via Veeam Cloud Connect.

The tenant configures for example a new Backup Copy job, selects the virtual machines he wants to protect off-site using Cloud Connect, and when it comes to the selection of the repository, the only difference compared to a regular job is that a Cloud Repository is selected:

5.20: Select a Cloud repository as the backup copy job target

Then, depending on the availability at the tenant’s side of a WAN accelerator, the job can be configured to leverage this capability or to use Direct mode:

5.21: Choose between direct mode or through WAN accelerators

The job can be completed and enabled, and both the tenant and the service provider can see it while it’s running.

This is the tenant view:

5.22: Tenant view of a backup copy job sending data to a remote Cloud Connect

And this is the provider view:

5.23: Service provider overview of incoming jobs from tenants

The service provider doesn’t have all the details the tenant has (for example, the real VM name is obfuscated), but it can check the progress and list how many jobs and virtual machines is receiving at any given time.