One item that doesn't get mentioned very often is making sure the client's
NIC configurations, and the switch port they connect to are the same.
We've found a couple clients that just s e e m e d t o d r a g o
n f o r e v e r. Delving into the issue, we found the NIC was set
for full-duplex, 100mbs, while the auto-negotiation of the switch's port it
was connected to was half-duplex, 100mbs. It's easy for the system admin
in charge of switches to set the switch port to a defined setting.
(Especially if they're using HP or 3Com switches, as we are here).
There are other issues as well but this one is well worth checking, as it
can affect the client's over-all performance on other protocols.
Best of luck,
Les Yaw
Luther College
Decorah, IA
At 01:07 PM 4/27/2004, you wrote:
I'm new to NetWorker and am looking for advice. What kinds of things can
causes sessions to become stuck? By that I mean the KB/s and total MB
as reported in the Devices area of nwadmin never change. I found a
KnowledgeBase article which talked about DNS issues casusing this but
are there other causes? I experimented with limiting savegroup
parallelism but that impacts the overall length of backups.
I know that some clients are extremely slow in backing up so am
wondering particularly if altering timeouts might impact anything.
Environment:
Legato 7.1.1 on Solaris
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
