Re: [Networker] 7.3.2 list of known problems

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of King, David
Sent: Thursday, November 30, 2006 11:57 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] 7.3.2 list of known problems

Listing the problems on 7.3.2 for posterity:  I'll add as people send
more to me.

        1. nsrauth problems (?)

        2. savepnpc post command problems. Post command does not fire
until the group is finished

        3. GUI problems.  Groups don't show finished until cloning is
done.

        4. drive target sessions problems.  7.3.2 ignores configuration
on Networker and uses its own.

        5. major media index problems.  (?)

        6. loss of command line functionality.  nsrjb relabeling  

        7. nsrjobd process that manage save job database could crash.
Rebooting every 3 hours to 2 weeks has been experienced.

        8. When a save is submitted, nsrmmgd error causes many tapes to
load before writing.  Possible fix is to kill nrrmmgd manually.


David L. King
>>>>>>>>>>>>>>>>>>>>


I've had some funky issues since going to v7.3.2 on RHEL4 at the
beginning of the November 2006.
1.  nsrexecd on the networker server aborted without any error being
generated in any log in the middle of a group incremental backup.  The
remaining save sets did not complete and no new scheduled groups were
started.  There is nothing present in /nsr/cores either.  Solution:
shutdown gst, shutdown networker.   Reverse the startup.
2.  Every now and again, the label information is lost for a tape and
the tape needs to be re-inventoried.  I think this may be the same issue
as #5 with the media index.  The tape label itself is fine, but
networker needs to collect the information again.  The problem is that
the tape(s) will not be used by networker until this happens and tape
requests remain pending.
3.  This may be the same as #6, I have to use the same tape drive for
any one tape pool labeling, relabeling activity.  In other words, it has
to be done one at a time to work from beginning to end.  If I let
networker choose to use more than one tape drive per pool, it becomes
confused and will not label some of the tapes.  The affected tapes need
to be done again.  Again, there is nothing wrong with the media or its
barcode.
4.  NMC does not display what is really happening in the group details
window under monitoring.  It will not display any save set actually
being processed, however it does know that the group is still in
process. If I check the mounted tapes for the pool, I can see data being
written by the percentage change and which save set is being processed.
5.  NMC will get hosed up and require not only a shutdown of the user
interface, but most times it requires the stop and restart of the gst
process.  Right now I have gst running on the networker server.  

 


Patti Clark
Unix System Administrator - RHCT
Office of Scientific and Technical Information

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER