Unsolved
This post is more than 5 years old
1 Rookie
•
18 Posts
0
8560
September 22nd, 2014 02:00
Error: savefs: Cannot retrieve the client resources.
We have migrated a server from Windows 2003 to Windows 2008. We have installed NetWorker 7.6 client on it. When the backup is fired, following error message is displayed, with backup getting failed:
90088:savefs: Cannot find the NSR group resource named 'winserver'.
90069:savefs: Cannot retrieve the client resources.
savefs winserver: failed.
winserver:savefs: retried 1 times.
Host files of server and client both have been checked and seem to be okay.
Please help.
No Events found!
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
September 23rd, 2014 04:00
Just to quick test: move client from existing group to new one (so create new group first which is called whatever you want except name of client and make sure it is in the pool that you want data to go) and start the group and see what happens. If you get the same, it is the issue with NSR client for sure.
m4nd4r
1 Rookie
•
18 Posts
0
September 23rd, 2014 04:00
In other cases, it is working absolutely fine.
Somebody had the exact same problem and he could resolve it by creating nsrauth auth methods after deleting nsr peer information. I did delete the nsr peer information, but I do not know how to create them. Please help.
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
September 23rd, 2014 04:00
So, your client is defined as shortname, right? If so, I suspect there might be a possibility of bug if group is called the same as client.... I never seen that before, but I also never had such scenario. If so, it should be easy to check it, but savefs response doesn't not check group so I suspect your client definition might something else "winserver" and you need to add "winserver" to alias list of existing client. It should be fairly easy to crack this down so you may wish to open a ticket with support and with webex they should be able to fix it within couple of minutes.
crazyrov
6 Operator
•
1.3K Posts
0
September 23rd, 2014 05:00
Peer information is created automatically, you don't have to bother about that. Was the new Windows 2008 server created from an image (eg: Gold disk) if so there is a possibility that the nsrla is holding the hostname of the old hostname. please provide the output of the following command from the client machine :
> nsradmin -p nsrexecd
nsradmin> . type: nsrla
nsradmin> print
nsradmin> quit
> hostname
josiel.sola
2 Posts
0
April 2nd, 2015 07:00
hi,
the solution is:
In your client, stop the networker service and in directory "Networker installation\nsr\" remove the directory "res".
start the networker service.
simple.
Josiel da silva sola
Compwire Informatica S.A
brazil.
Shihabi
1 Message
0
November 27th, 2017 02:00
Not sure if this question is resolved or not, but i faced the same issue in NW 9.1 all i did is copy the group and changed the policy to run using the copied group and backup is running now.