Re: [Networker] Novell client stability

We've had all sorts of problems with backing Novell clients, too slow,
errors sometimes that often clear themselves up after several weeks,
etc.  We've had to reboot Novell Servers every great now and then due to
Legato, but primarily just a reload of the NLM's works for us.

Taken from the Legato Knowledgebase (we had this problem at one
point):

If you get "Cannot make TSA connection" error etc.:

Ensure remote user and password is correct.
Ensure the remote user is a member of the SMS SMDR group object
in the NDS tree.

1. Ensure remote user in client setup has full context NDS name,
for example .CN=admin.O=Legato; also ensure this account
has adequate rights, meaning it should be able to login
to NWadmin (NetWare administration tools) and manage entire
NDS tree

2. Follow Novell TID#10017412 to recreate the SMS SMDR GROUP object
and reconfigure SMS environment.

Also note that tsands.nlm needs to be loaded if you want to backup
NDS via this machine.

The tsa500.nlm and tsands.nlm should be loaded earlier to allow the
tsa* nlms to be initialized properly prior to calling netowrkr.ncf.

>>> Craig Ruefenacht 11/19/03 09:50PM >>>
Howdy,

Recently we've been experiencing backup problems for most of our Novell

systems. The Novell OS ranges from v5.1 to 6.0 (not sure on the minor
versions because I'm not the Novell admin and hardly touch them).

They are all running fairly recent Networker client software (the
clients
that came with Networker 6.1 for the Novell 5 servers and the clients
that
came with Networker 6.1.3 for the Novell 6 servers). Our Networker
server
is v6.1.3, HP-UX 11i, and our tape storage is a SpectraLogic Gator
64000
with AIT-3 drives and AIT-2 media.

Until recently the Novell servers have been backing up without much
problem,
but lately most are failing. The servers themselves have not been
rebooted
in a while. We've tried to stop and start the Networker NLMs and there
was
no difference.

My question is, in general, for those who backup Novell using
Networker,
what kind of stability do you see in the backup process? Do you have to

reboot your Novell servers sometimes to massage Networker to work, does

simply reloading the NLMs work, or di you even have problems in
general?

Here is the unsuccessful saveset message we got yesturday. We've been
getting these the past couple of weeks. Nothing has changed on the
Novell
servers (such as admin passwords, access rights, etc), and no changes
have
been done on the Networker server either. As I said, these clients just

worked, and then one by one they started giving errors like the
following.
Rebooting our servers is an option, but we don't want to have to reboot
them
every time we have these problems show up.


Nov 18 20:48:33 apollo syslog: --- Unsuccessful Save Sets ---
Nov 18 20:48:33 apollo syslog: * slc-corp-s1:VOL2: 1 retry attempted
Nov 18 20:48:33 apollo syslog: * slc-corp-s1:VOL2: Backup: Cannot
restore
TSA connection to {slc-corp-s1.NetWare File System}SLC-CORP-S1
(0xfffdffc9)
Nov 18 20:48:33 apollo syslog: * slc-corp-s1:VOL2: (2000) ^IConnecting

directories failed
Nov 18 20:48:33 apollo syslog:
Nov 18 20:48:33 apollo syslog: * slc-corp-s1:VOL1: 1 retry attempted
Nov 18 20:48:34 apollo syslog: * slc-corp-s1:VOL1: Backup: Cannot make
TSA
connection to default NetWare server 0xfffdffc9
Nov 18 20:48:34 apollo syslog: * slc-corp-s1:SYS: has been inactive for
33
minutes since Tue Nov 18 20:15:18 2003.
Nov 18 20:48:34 apollo syslog: * slc-corp-s1:SYS: is being abandoned by

nsrexec.
Nov 18 20:48:34 apollo syslog:
Nov 18 20:48:34 apollo syslog: * slc-hr-s1:All 1 retry attempted
Nov 18 20:48:34 apollo syslog: * slc-hr-s1:All nsrexec: authtype rsh
Nov 18 20:48:34 apollo syslog: * slc-hr-s1:All Backup: Cannot make TSA

connection to default NetWare server (SMDR-5.0-16) The named SMDR is
unknown, does not exis
t, or is not loaded.
Nov 18 20:48:34 apollo syslog: Backup slc-hr-s1: failed.
Nov 18 20:48:34 apollo syslog:
Nov 18 20:48:34 apollo syslog: * slc-it-s1:All 1 retry attempted
Nov 18 20:48:34 apollo syslog: * slc-it-s1:All nsrexec: authtype rsh
Nov 18 20:48:34 apollo syslog: * slc-it-s1:All Backup: Cannot make TSA

connection to default NetWare server (SMDR-5.0-16) The named SMDR is
unknown, does not exis
t, or is not loaded.
Nov 18 20:48:35 apollo syslog: Backup slc-it-s1: failed.
Nov 18 20:48:35 apollo syslog:
Nov 18 20:48:35 apollo syslog: * slc-nw1:All 1 retry attempted
Nov 18 20:48:35 apollo syslog: * slc-nw1:All Connection refused
Nov 18 20:48:35 apollo syslog: * slc-nw2:All 1 retry attempted
Nov 18 20:48:35 apollo syslog: * slc-nw2:All Connection refused
Nov 18 20:48:35 apollo syslog: * slc-nw3:All 1 retry attempted
Nov 18 20:48:35 apollo syslog: * slc-nw3:All Connection refused
Nov 18 20:48:35 apollo syslog: --- Successful Save Sets ---
Nov 18 20:48:35 apollo syslog: * slc-corp-s1:{NDS} savegrp: suppressed
14
lines of output
Nov 18 20:48:36 apollo syslog: * slc-corp-s1:{NDS} (1) .NLS:License
ID=SN:403028057.NLS:Publisher=Novell+NLS:Product=NetWare 6
User+NLS:Version=600.OU=SLC.O=USANA
.[Root]^IUser has no access rights to the named object.
Nov 18 20:48:36 apollo syslog: * slc-corp-s1:{NDS} (1) .NLS:License
ID=SN:403030557.NLS:Publisher=Novell+NLS:Product=NetWare 6
User+NLS:Version=600.OU=SLC.O=USANA
.[Root]^IUser has no access rights to the named object.
Nov 18 20:48:35 apollo syslog:
Nov 18 20:48:36 apollo above message repeats 4 times
Nov 18 20:48:36 apollo syslog: * slc-corp-s1:{NDS} (1) .NLS:License
ID=SN:403033057.NLS:Publisher=Novell+NLS:Product=NetWare 6
User+NLS:Version=600.OU=SLC.O=USANA
.[Root]^IUser has no access rights to the named object.
Nov 18 20:48:36 apollo syslog: * slc-corp-s1:{NDS} (1) .NLS:License
ID=SN:301735144.NLS:Publisher=Novell+NLS:Product=NetWare 6
Server+NLS:Version=600.O=USANA.[Roo
t]^IUser has no access rights to the named object.
Nov 18 20:48:36 apollo syslog: * slc-corp-s1:{NDS} (1) .[Root]^I<<< BAD
MESSAGE >>>

--
Craig Ruefenacht
UNIX Administrator
USANA Health Sciences
http://www.usana.com

--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=


--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=