Case # 03763623
We had an issue where we could install the Agent directly onto the Physical Windows Server but it would not communicate with VBR Server
We were unable to install the agent from VBR as it failed with an RPC error on port 6160.
After much investigation and assistance with Veeam support, the ports it was trying to use showed as filtered. (port 6160 and 10001)
There was no Firewall running and AV was disabled but still we got the filtered response from portyquery. Test-NetConnection also failed.
Finally we rebuilt/reset the TCP/IP stack and disabled the Windows firewall and were finally able to install the Agent from the VBR server.
However we need to update the VBR server to latest version and although it stated 5GB Disk space is needed it looks like it needs more than 7GB after it copies and unpacks the files. It would be helpful if a temp directory could be specified as part of the install process.
Regards
-
- Service Provider
- Posts: 296
- Liked: 23 times
- Joined: Aug 10, 2016 11:10 am
- Full Name: Clive Harris
- Contact:
-
- Product Manager
- Posts: 14835
- Liked: 3082 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Win agent not connecting to B&R Server
Hello,
just to clarify: your feature request is to be able to specify the temporary folder for extraction during setup / update?
The request makes sense to me.
Best regards,
Hannes
just to clarify: your feature request is to be able to specify the temporary folder for extraction during setup / update?
The request makes sense to me.
Best regards,
Hannes
-
- Service Provider
- Posts: 296
- Liked: 23 times
- Joined: Aug 10, 2016 11:10 am
- Full Name: Clive Harris
- Contact:
Re: Win agent not connecting to B&R Server
Hi Hannes
that is correct.
Currently everything gets unpacked to the C:Drive and then copied to "packages" before the upgrade starts.
During the upgrade old files are copied to the C: Drive thus duplicating the space needed.
If a temp working directory could be created on a separate drive this would reduce the risk of failure on customers with small C: Drives
Sys requirements advises 5GB is needed, which may be true once the install/upgrade is finished but with the unpacking and copying this is nearer 10GB during the process.
Thanks
that is correct.
Currently everything gets unpacked to the C:Drive and then copied to "packages" before the upgrade starts.
During the upgrade old files are copied to the C: Drive thus duplicating the space needed.
If a temp working directory could be created on a separate drive this would reduce the risk of failure on customers with small C: Drives
Sys requirements advises 5GB is needed, which may be true once the install/upgrade is finished but with the unpacking and copying this is nearer 10GB during the process.
Thanks
-
- Product Manager
- Posts: 14835
- Liked: 3082 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Win agent not connecting to B&R Server
thanks - I just wanted to make sure because most of the post is about the issue you had before.
I will also check with the documentation team about the required disk space
I will also check with the documentation team about the required disk space
Who is online
Users browsing this forum: No registered users and 38 guests