-
- Novice
- Posts: 3
- Liked: 1 time
- Joined: Mar 20, 2017 9:09 pm
Trouble backing up to B&R server from remote host
A quick search of this board didn't turn up any answers to my issue, so I'll ask it here.
When configuring Agent for Windows to connect to my Backup and Replication server, so I can backup to my configured repository, I receive an error when the backup tries to run and fails.
"Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.10.8:2502"
The IP address in the error is the internal IP of my repository, which I use for all other backups made through my B&R server. However I suspect that that is the disconnect - I'm backing up from a remote host which is my web server. Perhaps I've missed configuring something about my repository, although I'm having no trouble with the initial connection to the B&R server from the remote host. I'm hoping that the remote host can use the B&R server as proxy to the repository; but perhaps the repository needs to be publicly accessible in a direct way?
Just to cover some questions I think would come up...
- my B&R server is version 9.5 update 1
- my B&R server can be reached by the Agent running on the remote host: I opened port 10001 and the logs in the Agent and in the B&R server show them communicating when the backup starts
- I've also opened ports 2500-5000 to the B&R server; I've read that they are used for the data transfer and one of them always shows up in the error message
When configuring Agent for Windows to connect to my Backup and Replication server, so I can backup to my configured repository, I receive an error when the backup tries to run and fails.
"Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.10.8:2502"
The IP address in the error is the internal IP of my repository, which I use for all other backups made through my B&R server. However I suspect that that is the disconnect - I'm backing up from a remote host which is my web server. Perhaps I've missed configuring something about my repository, although I'm having no trouble with the initial connection to the B&R server from the remote host. I'm hoping that the remote host can use the B&R server as proxy to the repository; but perhaps the repository needs to be publicly accessible in a direct way?
Just to cover some questions I think would come up...
- my B&R server is version 9.5 update 1
- my B&R server can be reached by the Agent running on the remote host: I opened port 10001 and the logs in the Agent and in the B&R server show them communicating when the backup starts
- I've also opened ports 2500-5000 to the B&R server; I've read that they are used for the data transfer and one of them always shows up in the error message
-
- Product Manager
- Posts: 14720
- Liked: 1705 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Trouble backing up to B&R server from remote host
Hi StJulienSean,
What type of VBR repository are you using? Generally, Veeam Agent should have a direct connection to the repository, so you need to make sure it’s accessible from agent’s machine.
What type of VBR repository are you using? Generally, Veeam Agent should have a direct connection to the repository, so you need to make sure it’s accessible from agent’s machine.
-
- Novice
- Posts: 3
- Liked: 1 time
- Joined: Mar 20, 2017 9:09 pm
Re: Trouble backing up to B&R server from remote host
I see. Well, I suspected that might be the problem. The repository for this example is a NAS.
Can't wait until Cloud Connect backup is possible direct from Agent. Right now my provider won't enable it because of the beta status of Agent.
Can't wait until Cloud Connect backup is possible direct from Agent. Right now my provider won't enable it because of the beta status of Agent.
-
- Product Manager
- Posts: 14720
- Liked: 1705 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Trouble backing up to B&R server from remote host
There is a ‘hack’ with a NAS box. Make sure that you established a direct connection between agent and you NAS gateway server. Once done you can backup directly to the repository bypassing VBR server.
-
- Service Provider
- Posts: 158
- Liked: 9 times
- Joined: Dec 05, 2014 2:13 pm
- Full Name: Iain Green
- Contact:
Re: Trouble backing up to B&R server from remote host
Having the same issue with a remote agent, in the logs i see it connects to the local IP of the machine rather than external IP address.
Reading here i now assume you can't connect an agent to a b&r server on different network unless using cloud connect?
Reading here i now assume you can't connect an agent to a b&r server on different network unless using cloud connect?
Many thanks
Iain Green
Iain Green
-
- Novice
- Posts: 3
- Liked: 1 time
- Joined: Mar 20, 2017 9:09 pm
Re: Trouble backing up to B&R server from remote host
I eventually managed to do it by connecting my remote host to my LAN through VPN, though I understand if this isn't the solution you're hoping for.
-
- Service Provider
- Posts: 158
- Liked: 9 times
- Joined: Dec 05, 2014 2:13 pm
- Full Name: Iain Green
- Contact:
Re: Trouble backing up to B&R server from remote host
Cheers tested on another machine through VPN and works. Will test on the remote PC later, can't see any reason for this not work.
Many thanks
Iain Green
Iain Green
-
- Product Manager
- Posts: 14720
- Liked: 1705 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Trouble backing up to B&R server from remote host
Hi folks,
True. Direct connect across WAN to Veeam B&R from Agent side is supported by cloud connect feature.Reading here i now assume you can't connect an agent to a b&r server on different network unless using cloud connect?
Also true. By setting up VPN you run agent and VBR is the same network, so routing is not an issue.I eventually managed to do it by connecting my remote host to my LAN through VPN
Who is online
Users browsing this forum: No registered users and 24 guests