Solved!
Go to SolutionClient not properly configured on the NetWorker Server.
Hello dears,
I'm a new to Networker, and I was working on setting up a client for backups on a windows OS.
I have installed the Networker client software on the client and also created the client on the Networker Management side however when I run the backup for the specified client I get 2 errors which are supposed to be for 2 different backup levels (Incremental) and (Full).
Here is the error I get for the Full backup:
Exited with exit code: 5, completion severity: ERROR(50), completion status: failed(1)
Here is the error I get for the Incremental level:
138851:save: 'ades1wn01aidfrv:E:\' is being reset/promoted to level 'Full' as no backup is found.
98519:save: Unable to setup direct save with server bkup: Client 'ades1wn01aidfrv' is not properly configured on the NetWorker Server..
90095:save: Cannot open save session with 'bkup': Client 'ades1wn01aidfrv' is not properly configured on the NetWorker Server.
ADES1PN01AIDFRV: E:\ level=full, 18 GB 00:00:00 56841600 files
Completed savetime=1533627760
90014:save: The backup of VSS emit save set 'E:\' failed.
99123:save: Handling an abort while processing Windows backup.
113712:save: Unable to perform the ASR backup: cannot obtain emitter status.
94693:save: The backup of save set 'pseudo_saveset' failed.
--- Job Indications ---
ADES1PN01AIDFRV:pseudo_saveset: retried 1 times.
And here is a screenshot of the client after it fails:
Can you please help to fix this problem and what is causing this error?
Any help is appreciated.
Thanks in advance.
26068
1
Posted August 7th, 2018 07:00
Not so easy because some core info is missing.
You are obviously running a NW 9.x version. This is all we can see.
What is your entry in the 'save set' Iist? - it is a bit unusual that only E: will be backed up. The default is 'all'.
Error code 5 usually stands for "Access denied". So I wonder which account you used to install the NW client software.
However, NW itself should not have any issues because it runs the backup with 'system' account.
Try to run a manual backup at the client first to verify whether you can backup at all. Do that for more than one volume:
save -s -b C:\
save -s -b E:\
one by one.
Let's see whether you can backup at all.
26068
1
Posted August 7th, 2018 22:00
Put this name to client alias… ades1wn01aidfrv
Lukas
26068
0
Posted August 8th, 2018 05:00
I already have that in the client alias; any other suggestions?
Thanks in advance.
26068
0
Posted August 8th, 2018 05:00
Sorry you are right I should've included those information at the first place.
- You are obviously running a NW 9.x version. This is all we can see.
- I am using Networker version 9.1.1.5
- What is your entry in the 'save set' Iist? - it is a bit unusual that only E: will be backed up. The default is 'all'.
- This is a File System backup which means we only backup the E partition so the Save Set is only "E:\". (we have similiar backups which are running fine as well btw)
- Error code 5 usually stands for "Access denied". So I wonder which account you used to install the NW client software.However, NW itself should not have any issues because it runs the backup with 'system' account.
- I have used a user to install the client which is created specifically for backup purposes and is a super user so it can't be a limitation from the user side.
- Try to run a manual backup at the client first to verify whether you can backup at all. Do that for more than one volume:
save -s -b C:\
save -s -b E:\
one by one.
Let's see whether you can backup at all.
- I tried to apply this suggestion from the client CLI and this is the result:
Thank you very much for your reply, appreciated.
26068
1
Posted August 9th, 2018 06:00
As I wrote before the message is clear, name is misconfigured/missing, check mistypes, maybe you can try stop NetWorker services to empty nsr/tmp on backup server to clean cache.
Lukas
26069
0
Posted August 9th, 2018 07:00
Hello,
can you post Client Properties with all TABS ?
Ty,
/C
26069
0
Posted August 11th, 2018 22:00
Hello dear,
The problem is solved, however, if you need this for a personal reference here they are although almost everything is default:
All the other tabs are empty or have default values.
Lawchak
1 Rookie
•
5 Posts
26068
1
Posted August 9th, 2018 06:00
Okay after a few days of troubleshooting I finally found the solution for this issue and it was because of the hostname which before was ades1Pn01aidfrv but after the OS was re-installed the name was changed to ades1Wn01aidfrv so I had to delete the client and re-create it again with that name and also put that in the client alias as Lucky85 mentioned. the issue is fixed now and the backup is completing successfully, thank you guys for your replies!