3.7 Cloud repositories

As suggested previously, it’s preferred to use a Windows or Linux server as a backup repository so a proper Veeam data mover service can be deployed on the repository machine itself. With this service properly deployed and running, all read and write operations are delegated to this service and all the available compute resources can be used by the data mover deployed locally on the backup repository.

SMB shares are supported by Veeam Cloud Connect, but even in this scenario, it’s advisable to deploy a dedicated Windows machine that will act as the gateway server (not to be confused with a cloud gateway) to directly communicate with the SMB share. The data mover will be deployed on this machine and not on other systems, especially the Veeam backup server, which should be only used as a management console:

Select a dedicated gateway server for SMB shares

3.12: Select a dedicated gateway server for SMB shares

This server will ultimately act like a proper repository machine. If Automatic selection is left as the default option, inconvenient selection like the VBR server itself may be done.

There are several design choices for a backup repository, and to list them all here will be simply impossible because many will be surely left out. Instead, this guide will describe two options: multiple Windows Server grouped together in a SOBR group, and a standalone Linux Server, both with local storage. This is not intended to suggest these are the best storage solutions; it is mostly an example to better describe the process of adding a backup repository to the Veeam Cloud Connect infrastructure.

Linux Backup Repository

lnxrepo
server name lnxrepo.cloudconnect.local
IP Address 10.10.110.51
Operating System CentOS Linux 7.0
Installed components none
vCPU 4
RAM 8 GB
Disk 20 GB, OS disk
Disk 1 TB, Backups disk

Networking is easy to manage for a Linux repository because only a control port is required:

Proto Source Port Destination Port Description
IPv4 TCP/UDP Linux_repositories * Domain_controllers 53 (DNS) Allow repositories to use internal dns
IPv4 TCP VBR_Server * Linux_repositories 22 Veeam VBR connects to Linux repositories
IPv4 TCP VCC_gateways * Linux_repositories 2500-5000 Gateways transfer data to Linux repositories
IPv4 TCP VBR_Server * Linux_repositories 2500-5000 VBR transfers data to Linux repositories

The entire management of a Linux repository is done using SSH. Because of this connection, the Veeam Backup & Replication server deploys a runtime component every time that starts the Veeam Data Mover using Perl (the only other requirement together with SSH), then transfers data using the usual Veeam ports 2500 to 5000.

Once the Linux server is added among the managed servers, the configuration of a new repository follows the usual process.

NOTE: Starting from CentOS 7.0, together with SSH and Perl you need to install manually also Perl-Data-Dumper. You can do so by running yum install perl-Data-Dumper

Select the path to be used as a Backup Repository

3.13: Select the path to be used as a backup repository

As explained in Chapter 2.7, concurrent tasks is an important parameter and should always be configured:

Configure path and load control

3.14: Configure path and load control

A typical Veeam Cloud Connect customer will be limited by the upload bandwidth that is available; this will be the main bottleneck in most of the use cases. However this does not mean it will be the primary bottleneck for the service provider: because the service provider is accepting several concurrent connections, the number of concurrent tasks connecting to the repository could be notable.

For this reason, a service provider needs to check the performance of a given storage solution, and needs to have room for enough concurrent connections so that customers tasks are not depleting the available resources. Please refer to chapter 2.7 and the "concurrency" paragraph for deep knowledge about how concurrency works in Veeam Cloud Connect.

In the Advanced options, it's also important to configure per-VM backup files: this option allows for better utilization of the storage and the tasks:

Configure per-VM backup files

3.15: Configure per-VM backup files

Linux repositories still need a Windows Mount server for file-level restores. It's suggested to use one of the other machines available in the same Storage subnet:

Configure the Mount Server

3.16: Configure the Mount Server

Because vPower NFS is not supported to date in Veeam Cloud Connect, a service provider can safely disable the configuration of this component during the repository creation wizard and complete it.

SOBR with Windows REFS backup repository

REFS1 REFS2 REFS3 REFS4
server name refs1.cloudconnect.local refs2.cloudconnect.local refs3.cloudconnect.local refs4.cloudconnect.local
IP Address 10.10.110.61 10.10.110.62 10.10.110.63 10.10.110.64
Operating System Windows 2016
Installed components Veeam Backup Repository
vCPU 4
RAM 16 GB
Disk 40 GB, OS disk
Disk 400 GB, Backups disk

These four servers are grouped into a SOBR group:

SOBR Group

3.17: SOBR Group

SOBR Group is using Data Locality policy to take advantage of REFS BlockCloning:

SOBR Data Locality Policy

3.18: SOBR Data Locality Policy

Finally, SOBR Group also has a Capacity Tier connected to it:

SOBR Capacity Tier

3.19: SOBR Capacity Tier

Networking requires a few more ports in order to manage a Windows repository, compared to the previous Linux repository:

Proto Source Port Destination Port Description
IPv4 TCP/UDP Windows_repositories * Domain_controllers 53 (DNS) Allow repositories to use internal dns
IPv4 TCP VBR_Server * Windows_repositories 6160 Veeam Installer from VBR to Windows repositories
IPv4 TCP VBR_Server * Windows_repositories 6162 Veeam Transport from VBR to Windows repositories
IPv4 TCP VCC_gateways * Windows_repositories 2500-5000 Gateways transfer data to Windows repositories
IPv4 TCP VBR_Server * Windows_repositories 2500-5000 VBR transfers data to Windows repositories
IPv4 TCP VBR_Server * Windows_repositories 49152-65535 Veeam RPC from VBR to Windows repositories
IPv4 TCP/UDP VBR_Server * Windows_repositories 137 - 139 Veeam SMB share access from VBR to Windows repositories
IPv4 TCP/UDP VBR_Server * Windows_repositories 445 Veeam SMB share access from VBR to Windows repositories

You can disable last two rules and enable them only when a new Veeam component needs to be installed or upgraded because Veeam uses SMB shares to deploy the installer packages into remote Windows servers like WAN accelerators and Windows-based repositories.

Once the Windows server is added among the managed servers, the configuration of a new repository follows the usual process.

Select the path to be used as a Backup Repository

3.20: Select the path to use as a backup repository

Again, as in the Linux repository, managing the ingestion rate of the repository is an important configuration aspect of the repository:

Configure path and load control

3.21: Configure path and load control

Finally, because vPower NFS is not supported to date in Veeam Cloud Connect, a service provider can safely disable the configuration of this component during the repository creation wizard and complete it.

Disable vPower NFS

3.17: Disable vPower NFS

Once the backup repositories are deployed and configured, Veeam Cloud Connect is ready to be consumed for backup services.

results matching ""

    No results matching ""