Comprehensive data protection for all workloads
Post Reply
Oletho
Enthusiast
Posts: 67
Liked: 2 times
Joined: Sep 17, 2010 4:37 am
Full Name: Ole Thomsen
Contact:

Error upgrading to v5

Post by Oletho »

At the end of v5 upgrade I get the error "Setup was unable to start VeeamNfsSvc service", and installation rolled back leaving me with neither v4 nor v5 :oops:

Windows (server 2008 R2) eventlog says

The Veeam vPower NFS Service service terminated with the following error:
%%-2147467259


What to do?

Ole Thomsen
Vitaliy S.
VP, Product Management
Posts: 27055
Liked: 2710 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Error upgrading to v5

Post by Vitaliy S. »

It would be best if you could open a support ticket with our technical team. Please attach a setup log file from %TEMP% folder located on your backup server. Thanks!
Oletho
Enthusiast
Posts: 67
Liked: 2 times
Joined: Sep 17, 2010 4:37 am
Full Name: Ole Thomsen
Contact:

Re: Error upgrading to v5

Post by Oletho »

I solved it myself, or kind of...

Veeam NFS Service uses the same port 111 as Networker Backup agent. When it cannot get exclusive access to this port setup fails and rolls back.

After stopping Networker agent setup succeeds.

I need the backup agent for getting backup files to tape, so next thing is to investigate if NFS service or Networker can be moved to another port number.

Ole Thomsen
Gostev
Chief Product Officer
Posts: 31457
Liked: 6647 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Error upgrading to v5

Post by Gostev »

Ah, I should have guessed the NFS port was already occupied by something else *facepalm*...
Simply no other reason for vPower NFS service to fail at start!
Oletho
Enthusiast
Posts: 67
Liked: 2 times
Joined: Sep 17, 2010 4:37 am
Full Name: Ole Thomsen
Contact:

Re: Error upgrading to v5

Post by Oletho »

If Networker agent is running NFS service refuses to start.

But if NFS is started first, Networker service also starts and backup works. Looks as if they are sharing port 111.

Configured Networker service for delayed start and things work fine even after reboot.

Ole Thomsen
Post Reply

Who is online

Users browsing this forum: ante_704, Bing [Bot], morgel, restore-helper, Semrush [Bot] and 157 guests