Cloud Connect gateways

Cloud Connect gateways serve as the primary connection endpoints for tenant replication traffic, handling encryption and data transfer orchestration. These components are critical for service availability and performance, making proper sizing and redundancy planning essential.

In case of mixing services (Backup - Replication - CDP) onto the same Cloud Connect deployment, it is highly recommended to create dedicated Cloud Gateway (Pools) for each service as they require a different SLA and uptime.

Redundancy and Load Balancing

Deploy an N+2 redundancy model for production environments, providing at least two active gateways with one additional gateway for failover capacity. This configuration ensures service continuity during maintenance windows or unexpected failures while distributing load across multiple endpoints. Veeam’s built-in gateway failover automatically redirects tenant connections to available gateways without manual intervention.

Sizing

CPU: 8 cores (vCPUs) can manage bandwidth up to 10 Gbps.
RAM: 16 GB RAM for up to 500 concurrent tenant tasks.

These specifications scale linearly - environments requiring higher throughput (more than 500 connections per gateway) should deploy additional gateways rather than oversizing individual instances. For comprehensive sizing recommendations including concurrent task limits, refer to the VCCR POD sizing section.

Source: Veeam Help Center - Cloud Gateway System Requirements

DNS and TLS Certificates

Using DNS names instead of IP addresses and deploying verified TLS certificates is a best practice for production environments. This approach provides flexibility for infrastructure changes and ensures proper SSL/TLS validation for tenant connections.

For detailed gateway configuration procedures, including DNS setup and certificate management, refer to the Cloud Connect Gateway Settings documentation.