Hello,

You can directly specify the saveset and the backup is run independently so that I can not satisfactory brower the saveset from the console

Regards,

Yes , I have  also tried but its doesnt work so gud mention the saveset in manually.

Hi,

So when you put the saveset in manually, it doesn't work either?  Does this happen for just one client?  You will need to check the connection between these two machines.  Check that name resolution is ok and that the networker processes are running on the server and client.  Run a save of a small file in debug mode from the client and it should give you a more precise error information - 'save -vvvvv -D9 /usr/testfile > test_backup 2>&1'

-Bobby

Hi,

Try deleting the clients NSR peer information from the NW server as well.

nsradmin -p nsrexec

nsradmin> p type : NSR peer information ; name : client_name ( first try with fdqn & then with shortname of the client  ).

nsradmin> delete

Delete? y
nsradmin> quit

Then restart NW services on the client end.

HTH

Hari Prakash.

The machine from which you are doing this should be the client which I expect it is.  Further, make sure that username you use on that machine is listed on admin list.  If you are doing this from server itself, try this operation as root.