Operational Defect Database
BugZero found this defect 2243 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb2560
All Aliases Have Failed
Last update date:
9/6/2023
Affected products:
Veeam Cloud Connect
Affected releases:
ALL
Fixed releases:
No fixed releases provided.
Description:
Challenge
Tenant jobs fail with the following message: Target gate has rejected connection. Unable to establish target connection. All aliases have failed.
Cause
New cloud infrastructure components have been added, and all gateways are unable to communicate with tenant repositories; or the SP Veeam Server.
Solution
It’s important to note that the wording of the error may differ, but the root error (All Aliases Have Failed) will be the same.To resolve this, please ensure all gateway servers in the service provider infrastructure can communicate with the tenant(s) repository and the Service Provider's Veeam Server.For communication route, reference:As a note, private gateways are not recommended and are one of the more common scenarios to encounter ‘All Aliases Have Failed’. Veeam will attempt to load balance across all available gateways based on current tenant connections, and a gateway usable by a specific tenant can get selected, resulting in this error. In addition, a private gateway can introduce a 4-minute and 15-second delay on every task (disk) a tenant processes.
More Information
Veeam Cloud Connect 11 Reference Architecture (Source for above image) Cloud Gateway Network Settings Veeam Cloud Connect Used Ports
