Stan
You need to add an environment variable when updating from 7.1.2 to 7.1.3
NetWare 'no nsr client resource for client (Client_Name)' Solution ID:
legato65286
Here is the solution: On Windows server, set this as a system environment
variable; a reboot will be required. Known issue: LGTpa66146. If the parent
or child of this fix is installed on NetWorker 7.1.1 or 7.1.2 servers, you
will need to set an environment variable NSR_SUPPORT_NETWARE_4X=1 to enable
NetWare client support. When netware support is enabled the following
message will apprear in the daemon.log "Support for Netware clients is
enabled." Please contact Legato Customer Support if you have this problem
with newer releases. On Windows server, add a system environment variable
NSR_SUPPORT_NETWARE_4X and set it value to 1; a reboot will be required. For
Unix servers: the variable must be exported before starting up NetWorker
server daemons. For example, using /bin/sh or /bin/ksh
# nsr_shutdown -q
# NSR_SUPPORT_NETWARE_4X=1; export NSR_SUPPORT_NETWARE_4X
# nsrexecd
# nsrd
Here is the problem or goal: Error: 'no nsr client resource for client
(Client_Name)' Error: '(NetWare_client_long_name):(Save_set_name) No 'NSR
client' resource for client (NetWare_client_short_name)' Error: 'cannot
retrieve client resources for (NetWare_client_name) on (Server_long_name)'
You will also find you can not restore any NetWare data on 7.1.3
A patch was released last week from Legato.
Request a download from the Legato support team.
>The hotfix for LGTpa72413 ( for the netware recovery problem) for windows
platform is out.
Regards
Richard
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On
Behalf Of Stan Horwitz
Sent: Saturday, 19 February 2005 2:06 a.m.
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Problem backing up Novell servers
Hello fellow NetWorker gurus;
Last Tuesday afternoon, we added on additional tape library capacity to
our NetWorker server and upgraded from NetWorker 7.1.2 to 7.1.3. Our
server is a Sun Solaris box with a Sony PetaSite tape library connected to
it via fibre. We also have a storage node running on another Sun Solaris 9
box with NetWorker 7.1.3 too. The storage node is connected via SCSI to 12
Sony AIT-2 drives in a Qualstar tape library. Later that night, we had a
massive network outage for several hours. This was brought on by a change
in firewall settings. The Network Service people here say they backed out
all the changes they did that night.
As a result of that network outage, the backups of all systems that are
not on the same subnet as our NetWorker server failed. Since than, all six
of our Novell servers fail to be backed up. They all elicit the same error
in the savegroup completion log, that they cannot see the NetWorker
resource. I tried directing backups to both the NetWorker server and the
storage node. The results were exactly the same.
These Novell servers were mostly running the old NetWorker 4.2 or 4.21
client, but upgrading them to 4.22 did not resolve this issue. I am not
involved with managing any of these six Novell servers. I asked the two
people who do manage them to test reverse DNS lookups back to our
NetWorker server. The test failed. They can look up the FQDN for our
NetWorker and its one alias fine, but not the actual IP address or short
name with nslookup. This is consistent across all six Novell servers,
from what I can gather. All six, are spread across different subnets from
our NetWorker server.
Our Network Services people say they see no DNS issues and they insist
that all the changes they made last Tuesday were backed out. The Novell
guys say it must be the upgrade from 7.1.2 to 7.1.3. Going back to 7.1.2
is not an option for us because the nsrd daemon on 7.1.2 would crash on us
once in a while and LEGATO said to upgrade to 7.1.3.
So, if anyone on this list has any suggestions on how to deal with this
issue, please let me know. The ironic thing about this is that all six of
these NetWare servers are due to be phased out soon, but we need to get
the backups working until that happens.
I am actually taking a vacation day today. When I return to work on
Monday, I do plan to open up a call with LEGATO's tech support, but I
suspect they will bounce the issue back at us because the reverse DNS
queries all fail.
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
