Mike,
We have experienced similar problem on NetWorker 6.0.2 running on Tru64 Unix
4.0D. We did however find an error message in the daemon.log at the time
the group should have started: "11/02/02 22:11:25 nsrd: runq: NSR group
Weekly_26_jb7 exited with return code 3." I don't think I ever called
Support about it. We just chalked it up to our server being too busy on
occassion.
Hope this helps.
Marilyn Schultz
Mitchell International, Inc.
San Diego, CA
(858) 578-6550 x6513
-----Original Message-----
From: Moehlman, Mike [mailto:mmoehlman AT TXI DOT COM]
Sent: Thursday, November 07, 2002 9:46 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Networker not scheduling some groups/clients
Networker 6.1.2 - server edition (Sun branded Solstice backup)
Solaris 8, E220R (single cpu), L1000 jukebox with 2 DLT 7000 drives
1 client per group, 37 clients definitions and 40 clients licensed
Full backups schedule each business day (M-F)
After some careful checking, we have recently discovered that Legato is not
scheduling some groups/clients for backups. There is no trace that it even
tries - not even the "starting group_name (with 1 client(s))" message in the
/nsr/logs/messages file. No emails - good, bad or indifferent (this is bad
because we have relied on the emails to detect what failed). If you look at
the gui (nwadmin> group control screen), it plainly shows that the last run
was 2 days prior - not the previous night's date as it should be.
Within the past week, we have noticed 6 different groups/clients that were
not scheduled for processing over 4 different days (1 or 2 per day). Other
backups are active at the time the group/client was "scheduled" to start.
The group/client that was not scheduled appears to be random. I can not
recognize a pattern yet for which client or which day that it will "not
schedule" something. So far, the "missed" clients complete successfully the
following night.
Sun support suggested an L5/6 check on the client indexes. Ran clean
Suggested we recreate the problem client's indexes. Renamed the whole index
directory and let it create new ones for all of the clients.
Not going anywhere fast at this point.
Has anyone seen a similar problem? Suggestions for resolving?
--
Note: To sign off this list, send a "signoff" 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" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
