Job Writing to Cloud Connect Repository Fails with: "Target gate has rejected connection. Connection target is not recognized. No rule exists."
| KB ID: | 4314 |
| Product: | Veeam Cloud Connect | 10 | 11 |
| Published: | 2022-05-31 |
| Last Modified: | 2022-05-31 |
Challenge
Error Cloud gate has rejected connection. Reason: Connection target is not recognized. No rule exists.. (System.Exception)Error Connection target is not recognized. No rule exists. (Veeam.Backup.Common.CCloudGateNoRuleException)Cause
This issue most often occurs when an external load balancer or DNS Round-Robin has been configured between the tenant's environment and the Cloud Connect Provider's Cloud Gateways, which causes traffic to be sent to a Cloud Gateway other than the one assigned to the tenant's task.
As each task begins on the tenant's side of the connection, the Cloud Connect server creates a dedicated traffic forwarding rule for the backup traffic. This traffic rule is based on Veeam Cloud Connects internal load-balancer selecting the Cloud Gateway server with the least amount of tasks already assigned. Once the traffic rule is created, that tenant's backup activity is expected to use the designated Cloud Gateway and is not allowed to use any gateways where this rule does not exist.
An external load balancer or DNS Round-Robin breaks this logic and may cause tenant traffic bound to a specific forwarding rule to be sent to a different Cloud Gateway, resulting in the error mentioned above.
Here is an example of how that incorrect configuration will appear within the view in the Veeam Cloud Connect Console:
Solution
To prevent the issue described in the cause section, Veeam Cloud Service Providers should avoid external load balancing for Cloud Gateway traffic.
Here is an example of a correctly configured set of Cloud Gateway servers, each with their own distinct DNS and IP address.
More information
- For high availability reasons, Veeam Cloud Service Providers can use DNS Round-Robin and external load balancers only for the name of the Service Provider when adding it to a tenant VBR server:
https://helpcenter.veeam.com/docs/backup/cloud/cloud_connect_sp_settings.html
Cloud Gateway Configuration example from VCC Best Practice Resource: Load Balancers - Please keep in mind that Veeam has its own HA logic and keeps the names of all available Cloud Gateway Servers obtained from SP during a previous rescan or job run. This allows the tenant VBR server to automatically failover to the next gateway if some gateways are offline.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.