To be able to back up to the iland cloud successfully, your Veeam Backup and Replication (VBR) server will need to communicate all the way through to the iland cloud gateways and then to your cloud repository. However, some customers find that they experience connectivity problems when they try adding iland as a service provider or when they attempt running their backup copy job. The following article covers practical steps to perform basic tests that will help you determine if the problem is likely to be on your side (for example, firewall port restrictions) or on iland's side.
In regards to the latter, please check the iland's status page for any maintenance notifications to rule out a planned event which may be the cause of the connectivity problem. We recommend that you subscribe to the status page to get important notifications about your iland service.
If you are blocking outbound connections from your environment, you will need to allow connections to the iland cloud gateways. As the connection to the tenant is encrypted using a certificate you will also need to allow outbound connectivity over HTTP and HTTPS which allows your Veeam server to verify the Certificate Revocation Lists.
To establish the correct IPs of the Cloud Gateway, you can use the FQDN of the service provider URL that was provided by the project team during the initial deployment of the service. Open Command Prompt on the Veeam server and type 'nslookup'. Then, type the FQDN within nslookup. The results are the IPs associated with the service provider URL.
In this example, we are using a test record and the IPs associated with it are private IPs. In real life the the service provider will have a public IP range associated with it.
Note: Pinging the FQDN to find the IPs will only display one of many.
The firewall rule you create should have the following form:
Your VBR server
Your local repository
IPs of iland Cloud Gateways
TCP and UDP port 6180
|Your VBR server||Outbound||TCP port 80 and 443||Allow|
In order to test connectivity, you should perform a connectivity test from your VBR server and your local repository. The port that is used is 6180. The test should be performed to each of the iland Cloud Gateways.
You can use the following PowerShell command to test:
New-Object System.Net.Sockets.TcpClient("IP address", 6180)
If the returned state of Connected is True then the port is open.
You can also use the telnet command to test. Open Command Prompt and type 'telnet [IP of Cloud Gateway] 6180'
If you see a blank cursor then the connection is fine. You can close the command prompt window.
If you get the following message you will need to install the telnet command on your system.
Telnet is not recognized as an internal or external command, operable program or batch file.
To do that, follow these steps:
6. You can click “Close”.
If you get an error or are unable to telnet to the server, please double check your firewall settings.
Please make sure to test from both the VBR server and the repository and to test to all of the iland Cloud Gateways backing the service provider URL.
After performing these tests, the chances are that you will have some idea as to what may be wrong and would have taken a corrective action such as changing a configuration on your firewall. If that is not the case and you suspect that issue is on iland's side, or you simply want advice and further suggestions, please make a note of the output of your tests and provide it to the iland support team for further investigation and suggestion.