Unsolved
This post is more than 5 years old
18 Posts
0
8304
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.
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
September 22nd, 2014 02:00
Assuming these backups were working prior to the migration.
Follow this.
- Uninstall the NetWorker client 7.6
- rename the directory C:\Program Files\Legato
- Install the NetWorker 8.1.1.x client binaries on this server.
- Test backups.
m4nd4r
18 Posts
0
September 22nd, 2014 02:00
Is there any alternative to this?
At this moment, we do not prefer this action to be taken due to some restrictions.
pawankumawat
355 Posts
0
September 22nd, 2014 03:00
Hello,
Please verify ping and nslookup is working fine.
Make sure that the alias associated with the client is specified in the aliases field of the associated client resource
Rename nsrladb and restart Nertworker client services.
Hopefully It should resolve the issue.
Regards,
Pawan
ble1
2 Intern
2 Intern
•
14.3K Posts
0
September 22nd, 2014 03:00
You might be missing alias or something... go to client and run savefs -s -vpn and see what does it say. If it says hostname is missing then most likely you have FQDN definition of client and you need to add it to alias list of the client.
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
September 22nd, 2014 07:00
pawankumawat ,
i guess you meant the nsrladb folder inside the nsr folder ?
pawankumawat
355 Posts
0
September 22nd, 2014 07:00
Yes and Thank you
I could have been more specific.
Regards,
Pawan
m4nd4r
18 Posts
0
September 22nd, 2014 20:00
Hi Pawan,
Thanks for your response.
Ping and nslookup are working fine. I have also added host entries in the 'hosts' files of both server and client.
I have also verified the alias and it seems to be perfect.
The main issue is that I could not find nsrladb folder in nsr directory of the client. Can you please confirm the location of this folder?
Note: Client is a Windows 2008 server.
KobusStrydom
18 Posts
0
September 22nd, 2014 21:00
Please can you post output for the following commands.
From backup server run “rpcinfo –p winserver”
From client run “rpcinfo –p ‘backup server name’
KobusStrydom
18 Posts
0
September 22nd, 2014 21:00
I know you’ve tried this from client side, but please can you try from server side and post output.
Savegrp -vvv –L full –c winserver –G winserver
Kind Regards
Kobus Strydom
27 71 680 8142
m4nd4r
18 Posts
0
September 22nd, 2014 21:00
savegrp -vvv –l full –c winserver –G winserver
7266:savegrp: Only one group name allowed
usage: savegrp [ ] [-R | -G] [groupname]
: [-EIOFVbmnpv] [-l level | -C schedule] [-e expiration time]
[-w browse time] [-y retention time] [-t date] [-r retries]
[-P printer] [-W width] [-c client ...]
KobusStrydom
18 Posts
0
September 22nd, 2014 21:00
I see earlier post mention "90088:savefs: Cannot find the NSR group resource named 'winserver'
and your last post 90088:savefs: "Cannot find the NSR client resource named 'winserver'"
Is 'winserver' a client or a group resource?
m4nd4r
18 Posts
0
September 22nd, 2014 21:00
Hi Kobus Strydom,
In order to avoid confusion, we create the group with a name same as the client's. So, there is a group 'winserver' with a client 'winserver' in it.
Following error was displayed in the NetWorker Management console:
90088:savefs: Cannot find the NSR group resource named 'winserver'
Following error was displayed when i executed savefs -s -vpn on client.
90088:savefs: Cannot find the NSR client resource named 'winserver'.
m4nd4r
18 Posts
0
September 22nd, 2014 21:00
Hi Kobus Strydom,
The output is as follows:
From Backup Server
rpcinfo -p winserver
program vers proto port service
100000 2 tcp 7938 portmapper
100000 2 udp 7938 portmapper
390436 1 tcp 8289
390435 1 tcp 8346
390113 1 tcp 7937 nsrexecd
From the Client
program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390436 1 tcp 9046
390435 1 tcp 8559
390113 1 tcp 7937
390103 2 tcp 8386
390109 2 tcp 8386
390110 1 tcp 8386
390120 1 tcp 8386
390109 2 udp 8730
390107 5 tcp 8065
390107 6 tcp 8065
390114 1 tcp 8075
390439 1 tcp 8786
390433 1 tcp 9161
390105 5 tcp 8170
390105 6 tcp 8170
390438 1 tcp 9696
390430 1 tcp 7964
390429 101 tcp 8148
390111 1 tcp 7955
390104 205 tcp 8174
390104 305 tcp 9821
program vers proto port
100000 4 tcp 111
100000 3 tcp 111
100000 2 tcp 111
100000 4 udp 111
100000 3 udp 111
100000 2 udp 111
100024 1 udp 26365
100024 1 tcp 26989
390402 1 tcp 9001
390436 1 tcp 9046
390435 1 tcp 8559
390113 1 tcp 7937
390103 2 tcp 8386
390109 2 tcp 8386
390110 1 tcp 8386
390120 1 tcp 8386
390109 2 udp 8730
390107 5 tcp 8065
390107 6 tcp 8065
390114 1 tcp 8075
390439 1 tcp 8786
390433 1 tcp 9161
390105 5 tcp 8170
390105 6 tcp 8170
390438 1 tcp 9696
390430 1 tcp 7964
390429 101 tcp 8148
390111 1 tcp 7955
390104 205 tcp 8174
390104 305 tcp 9821
m4nd4r
18 Posts
0
September 22nd, 2014 21:00
Hi Hrvoje Crvelin,
Thanks for responding.
When I executed the mentioned command on the client, following error message was displayed.
90088:savefs: Cannot find the NSR client resource named 'winserver'.
90069:savefs: Cannot retrieve the client resources.
Any suggestions?
KobusStrydom
18 Posts
0
September 22nd, 2014 22:00
From server command line run
“nsradmin –d “install path\nsr\res\nsrdb” for unix, change /nsr/res/nsrdb”
(at the prompt enter text exactly as shown)
Nsradmin> . type : nsr client ; name: winserver
Nsradmin> p
Copy and post output
Same for group
Nsradmin> . type : nsr group ; name: winserver
Nsradmin> p
Copy and post output
Kind Regards
Kobus Strydom
27 71 680 8142