3.2 Veeam Cloud Connect Backup deployment

Once VLANs and subnets are created, and the firewalls are in place to protect communications between the different security zones, it’s time to deploy the different servers needed and suggested to build the complete Veeam Cloud Connect Backup environment.

This is the schema of the servers:

3.2: Cloud Connect Backup servers details

The internal domain is named cloudconnect.local and is managed by two DNS servers 172.27.217.21 and 172.27.217.22; they need to be configured in all other servers of the Veeam Cloud Connect infrastructure.

Cloud Connect POD sizing

The sizing described here is recommended for up to 1000 concurrent tasks, which is the maximum amount of tasks manageable by a single VCC POD. This value has been tested with:

250 tenants with 4 tasks each, with worst possible scheduling (everything kicks in in parallel)

For additional information, also refer to the relevant section of the Veeam Service Providers Best Practices.

Veeam management servers

In previous versions of this book, we used to suggest the installation of Veeam Enterprise Manager. This had two goals:

• expose the RESTful API for automation
• install the Cloud Connect Portal for accessing and executing Failover Plans

Since the release of Veeam Service Provider Console (VSPC), both these two capabilities are available in the console, together with many more amazing features. So, we now suggest to install directly VSPC and manage Veeam Cloud Connect through it.

This server holds the installation of Veeam Backup & Replication. In a Veeam Cloud Connect infrastructure, this server is the central location for daily activities, unless VSPC is used.

The installation has no specific requirements, and you can follow the default wizard from start to finish. A PostgreSQL database is needed to store all the configuration and data, and it can be installed directly into the VBR server (as part of the installation wizard) or it can be manually installed in a dedicated machine before installing VBR.

Once the setup is completed and the license to enable Veeam Cloud Connect is installed, the initial management interface can be reached by opening the Veeam console and selecting the node Cloud Connect:

3.3: Veeam Cloud Connect start screen

From here, the required steps to have a fully functional Veeam Cloud Connect Backup infrastructure are:

1. Create and install a proper certificate (see Chapter 8.1 and Chapter 8.2)
2. Deploy and configure the required cloud gateways
3. Deploy and configure the optional WAN accelerators
4. Deploy and configure at least one backup repository

Once all the configurations steps are completed, a service provider will be able to create and manage users/tenants.