During the beta for VAL there was a known issue for sending backups to VBR. We are now re-testing with VBR 9.5U1 and the latest VAL on an ubuntu system hosted at a cloud provider.
We seem to get further than during the beta but still having an issue. The VAL or VBR server (not clear which) is pointing to the "wrong" place.
- Code: Select all
16:18:37 Starting full backup to [svr-bkp-01]repo-01
16:22:57 [error] Failed to perform backup
16:22:57 [error] Failed to connect to the port [192.168.60.31:2500]
The complete data path is as follows:
[Cloud ubuntu] --> [firewall NAT @ customer lab] --> [VBR server] --> [Create Backup Data]
The IP address 192.168.60.31 is a valid IP for the VBR server, but this is a secondary NIC on a closed network for storage (iSCSI). By observing firewall logs I see the initial connection works fine and a small backup file of a few KB (.VBM) is even created in the assigned backup repo, however soon after the job fails with the above error message.
The iSCSI storage is mounted at the windows level and is visible as a local drive letter to the VBR server, and is configured as local storage in VBR (windows server), so there is no need for veeam itself to be trying to access this network.
I've tried creating an entry in the VBR server's hosts file for the correct IP for the machine name (svr-bkp-01) but this did not help.
Are there any specific configurations required for this to work?
If required I can test with a NAS-based repo but the customer would prefer the backups all go to his iSCSI device.