Link Search Menu Expand Document

Production design

Even though it is technically possible to create Single-Server installations (also called All-in-one installations) for each of the service administration solutions, it is against all the best practices for a production deployment and therefore should only be used during a Proof of Concept (POC).

In a production environment, the recommended deployment is to spread out the different roles/services onto different servers. This way we can balance the load and add more resources to specific components when needed.

Order of deployment and dependencies

VSPC uses the tunneling technology of Veeam Cloud Connect (VCC) to create secure connections over public networks to the remote components such as Veeam Agents and Veeam Backup & Replication servers. Even if VSPC is only used for remote monitoring or licensing, VCC needs to be deployed.

As both solutions require a SQL database to store its configuration, we need to either install MSSQL Server first or re-use and existing MSSQL Server installation.

The different components should be installed in the following order:

  1. Database Server
  2. VCC Server
  3. VCC Cloud Gateway
  4. VSPC Server
  5. VSPC Web UI

Veeam Cloud Connect (VCC)

Components

Similar to VSPC, all VCC components can be installed on a single Windows machine. This will combine all of the following components onto the same machine:

  • Database Server
  • VCC Server
  • VCC Cloud Gateway

Veeam Service Provider Console (VSPC)

Components

This will combine all of the following components onto the same machine:

  • Database Server
  • VSPC Server
  • VSPC Web UI

Design

The production design has separate Windows machines for each of the components.

Modular architecture


Back to top

Copyright © 2019-2022 Solutions Architects, Veeam Software.