Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

RAP error: unsupported authentication type

Status
Not open for further replies.

sunt

MIS
Nov 6, 2002
29
US
Hi,
I found the following messages in the daemon.log and finally the savegroup was failed. The group was failed during the backup only a few GB of the hard disk has been backed up. This happened on D drive, the C drive is ok.
Any comments? Thanks in advance!
Tony

11/12/02 03:03:27 savegrp: RAP error: Unsupported authentication type
11/12/02 03:03:27 savegrp: RAP error: Unsupported authentication type
11/12/02 03:03:27 savegrp: Failed to contact server, aborting Savegroup.
11/12/02 03:03:52 savegrp: group GROUP1 aborted.
11/12/02 03:03:52 savegrp: killing pid 174
11/12/02 03:04:00 nsrd: savegroup alert: GROUP1 aborted, 1 client(s) (group1client Failed)
11/12/02 03:04:00 savegrp: RAP error: Unsupported authentication type
11/12/02 03:04:00 savegrp: Failed to contact server, aborting Savegroup.
11/12/02 03:04:00 savegrp: RAP error: Unsupported authentication type
11/12/02 03:04:00 savegrp: lost 'NSR group' resource with name 'GROUP1'.
11/12/02 03:04:00 nsrd: runq: NSR group GROUP1 exited with return code 1.
 
Looks like there is a network communication issue.

Usually when I see a return code one, it is usually (but not always) related to name resolution.

Check out tech bulletin 299: IP Naming in Heterogeneous Environments, and follow the tests to confirmt hat your network is configured properly.



Where is the d: drive? Is it a mapped drive? Is it consistently failing all the time? Try specifying saveset=d:\ and try backing up again.

Also use the NetWorker user gui on the client and try a manual backup to see if it backups up the d: drive.
 
This case is very strange. Like last Saturday, the backup is successful. lastnight it get failed again. The case is it always get failed on this specific client's D:\ and always happened at the middle of the backup, the savegroup did start and seems backup ok at the begining. However, it failed at the middle. D drive is the local hard drive of the client.
I have follow the bulletin 299, seems everything is ok.
When I do a manual backup, most of the time it can get through and successful. I have a seperate savegroup for this client, that means only one client backup during that period of time ( no overlapping). Will it be any problem on the client side?
Thanks
 
Manual backups work *most* of the time? When and why would it not?

Could it be that it is a permissions issue with the d: drive; i.e. there is a ACL that is preventing NetWorker from reading the data on that drive? Remember, by default, the NetWorker Remote Exec Services in the client is started using the SYSTEM account. You usually are loggin in using the Administrator account. Check ACL's and file permissions.

Like I said, try defining the client with only d:\ as the saveset and run the savegrp backup. Do it from the command line, and stick in some verbose arguments:

savegrp -vvv -c <client> -s server -l f <Group> >test1.log 2>&1

Also repeat with debug option:

savegrp -D9 -c <client> -s server -l f <Group> >test2.log 2>&1
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top