- Posts: 1
- Liked: never
- Joined: Mar 24, 2020 12:38 pm
- Full Name: James Simmons
I'm having some trouble and I'm just wondering if anyone else is in the same boat.
I have an off-site Synology NAS that is being used directly as a Linux server repo.
I have one job that runs nightly on this repo, and it has been running flawlessly for a few months now.
All of a sudden I'm getting a "Failed to connect to the port hostname:2500" error.
What's strange is I'm still able to rescan the repo, look at files, and health checks even still work.
But when it's time to actually move data it completely fails. namp and netstat tell me the port is indeed open and the Veeam agent is established on the port.
I've ruled out firewalls and whatnot by disabling everything before trying.
My only change I've made is a changed my main backup job from an SMB share to a direct windows agent.
Anyone else had this issue with their Synology NAS's recently?
- Veeam Software
- Posts: 731
- Liked: 100 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
As far as I understand you're talking about backup copy job?
The only idea which comes to my mind is that the connection needs to be established between the new Windows server (new repository for primary job) and the Linux repository and there is some problem with that.
Other operations like rescan or file lookup work because there are no connectivity issues between Veeam server and the Linux repository. Anyway, let's wait for results of investigation from our support team.
Users browsing this forum: No registered users and 16 guests