Availability for the Always-On Enterprise
Post Reply
Veeam Vanguard
Posts: 32
Liked: never
Joined: Apr 30, 2013 1:19 am
Full Name: Yukinobu Asami

Windows FLR failed, when we change the Data Mover port

Post by Yukinobu » Jan 30, 2017 1:00 am


Windows FLR failed by following error, after we change the port of Veeam Data Mover service(on Veeam Backup server) to 7162(Change value at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Veeam\Veeam Backup Transport\Port).

RPC server unavailable. RPC function call failed. Function name: [InvokerTestConnection]. Target machine: [] is Veeam Backup server.
We confirmed Svc.VeeamMount.log.
Veeam Mount service used the default port instead of the changed port of Veeam Data Mover service.
[26.01.2017 09:45:56] Error Failed to connect to Veeam Data Mover Service on host 'ASAMITEST2012R2', port '6162' (System.Exception)

If we return setting change( to 6162 port), Windows FLR is successes.
So the cause is that Veeam mount service can not refer to the correct port number of Veeam data mover service.

We already confirmed this problem to Veeam support(Case # 02050573).
"This is by system design, unfortunately. And if you changed that port, it wont work."

Please take care, when you change the port.


Post Reply

Who is online

Users browsing this forum: Exabot [Bot] and 22 guests