While I don't want to complain  I must commend you on your bug/oddity list.
I can only pipe in with a "me too".   I can say I:

a.) Have SYSTEM STATE failing on the webtrends clients.  We're zeroing
in on nonpagedpoolsize but have no solution yet.

b.) Have not had experience with NDMP on 7.1.1 yet but am concerned now.

c.) Have some Netware clients and realize the drawbacks.

d.) Have groups that hang forvever on a client.  While its always a client
issue (the probe might be stuck) that group can hang for days unless someone
catches it. No timeouts are honored.  Its been mostly 6.2 clients that
do this but from a design point a view its troubling; one client can cause
the backups not to run.

e.) The clients looking up the server name cause failures all the time if
the DNS name is not appended. Fixed with host file entries on the client it
becomes worst as one cannot change the server network interface for the
client or storage node without those lookups failing.

Altogether a good summarized listing.


Robert Maiello
Pioneer Data Systems


On Tue, 8 Feb 2005 13:55:23 +0100, Oscar Olsson <spam1 AT QBRANCH DOT SE> wrote:
...
>Well, as long as you are aware of the quirks and bugs, you can learn to
>live with it. But as a previous poster said earlier in this thread, I also
>experience that I have to babysit Networker too much due to too many
>oddities and possible bugs.
>
>For instance:
>
>* SYSTEM STATE fails to back up intermittently on machines running
>webtrends.
>* NDMP support in 7.1 is still flaky and feels unreliable in general
>* The NDMP tape device fails to mount upon restart of networker, since
>7.1.3
>* Netware support is still flaky, and requires a debug variable in 7.1.3
>* Some savegroups never time out, they just hang forever, intermittently,
>especially if they have netware clients in them.
>* Name resolution is severely broken in 7.X, one must thus use the short
>name as an alias, which can't be resolved if you don't control naming of
>hosts.
>
>I don't mean to whine, but rather share my experiences with the community,
>so that we can get a better product from EMC. I guess its a combination of
>initial product stability and level3 support that makes it frustrating at
>times to use networker.
>
>//Oscar
>
>--
>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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=