Failed to connect to the port 2501

[ithk]

Hi,

I have a issue on backup copy job on my offsite storage.

My veeam structure is:
One veeam server connected with two backup repositories. One repositories is in office(repositories 1) and one is in datacenter (repositories 2).
Normal backup jobs will store in repositories 1, and want a offsite backup to repositories 2.
So we plan to have a backup copy job to repositories 2 but we get the Error: Failed to connect to the port [repositories 2 IP:2501].
Is it i have get the wrong setting on the jobs?
I can success backup VM to repositories 2 directly.

Thanks,

[Mike Resseler]

Hi Asiatoday,

First: Welcome to the forums!
Second: When you do a backup copy job, it will be from repository to repository. So if those repositories are other VMs or servers than the Veeam server (like a windows box or so) then you need to have that connection open. In the first case, you are doing the work from Veeam server to repository A and B.

You can see the ports (and the explanantion) here: https://helpcenter.veeam.com/docs/backu ... =95u4#repo

[ithk]

Thanks Mike~
i have solved the connection problem.
It success started the job but get error and fail finally.

19/2/2019 9:50:03 AM :: Processing Server1 Error: File [/home/exagrid/veeamdc/backups/Backup Copy Job 2_1/Server1.2a0af13c-da7d-df11-b446D2019-02-18T095322.vbk] is locked.
Failed to restore file from local backup. VFS link: [summary.xml]. Target file: [MemFs://RestoreText_{7897ba8b-0bbb-4094-a49a-22facd1780b4}]. CHMOD mask: [0].
Agent failed to process method {DataTransfer.RestoreText}.

And don't know why the vbk is locked.

[Mike Resseler]

Hmmm,
Did you only open the one specific port between the two repositories or the range (as can seen in the documentation)

Thanks
Mike

[ithk]

Hi Mike,

No, i have allowed all the port.
And is it related to the network speed between two repositories? i see that only have 20MB/s transfer, but my full backup have 2.4TB.

[Mike Resseler]

Hey,

Please open a support case. It might be that there is still something wrong with the ports or this is a separate case.
Please post the case ID and the outcome after our engineers investigated

Thanks
Mike