Backup Licenses - Troubleshooting guide

This covers the case where the Add Service Provider wizard fails in your Veeam Backup & Replication console: the connection to our infrastructure does not go through.

Check that your firewall allows the outbound connection from your VBR server to our server, that is, to the cloud gateway DNS address provided in your delivery email (in the form vspc-adv-cgw…), on port 6180.

Also check that:

• the DNS address and port entered in the wizard exactly match those in the delivery email;
• the Company Tenant credentials you entered are those from the delivery email;
• your VBR server runs version 12 or higher (see the known restrictions).

This covers the case where the wizard completed without an error, but the server does not appear — or appears as unreachable — in the VSPC. The outbound connection works; it is the return path to your server that is blocked, or the management agent that was not deployed.

Check the following two points:

• Your firewall allows connections to your server from our IP address. In Europe, our infrastructure reaches your VBR server from the address 79.137.44.43, without restriction.
• You ticked the Allow this Veeam Backup & Replication installation to be managed by the service provider option when adding the service provider. Without this option, the management agent is not installed and your server cannot be managed from the VSPC.

If the option was not ticked, edit the service provider from your VBR console (Backup Infrastructure > Service Providers > right-click > Edit provider), tick the option, then run the wizard through to completion.

If MFA (multi-factor authentication) is enabled on the connected VBR server, it may appear with the Inaccessible status in the VSPC.

See Veeam KB 4431 for the resolution procedure.

In the Veeam Backup & Replication console, open the main menu and click License to display the License Information window.

• If the status is not Valid, first check that your VBR server is correctly connected to the VSPC (see the first two points on this page).
• Check that the edition displayed matches the one you ordered, and that your operating system is compatible with that edition (see the known restrictions).

If the issue persists while the connection is established, contact OVHcloud support, providing screenshots of the License Information window.

Do not connect a VBR server that is already connected to the VSPC using different credentials: this skews the data displayed in the VSPC.

Remove the duplicate service provider from your VBR console (Backup Infrastructure > Service Providers > right-click > Remove provider), then keep only the connection matching your currently valid credentials.

If your VBR is the primary node of a high availability cluster, the VSPC registers it as a cluster node. The secondary node must be connected separately, following the same service provider procedure.