On Oct 1, 2006, at 11:04 PM, Prasad Chalikonda wrote:
Hello,
Setup is as follows:
Networker 7.3.1
1 Server
5 Storage Nodes - for backing up BCVs & clients
2 Storage Nodes (for running eseutil - just for
Exchange BCVs)
All data goes to CDL first, then cloned to tape.
According to the network folks, the LAN had crashed
twice last week,
during clones. Not during backups, but during clones.
They determined
this by noticing a spike in the network traffic going
to the NetWorker
server, when the cloning started.
At first they thought data (clone data) was going over
the LAN. But
after reviewing the configuration (Storage node
attribute, and Clone
Storage node attribute) for all clients, I feel sure
there is no data
being sent over the network. So whatever traffic the
NetWorker server is
seeing, should be just metadata from the storage
nodes, right? Could
this be of such a magnitude that it would case the LAN
to crash?
They are trying to isolate the problem, which at this
point looks like
it is happening only during Exchange BCV cloning. The
only explanation I
could come up with so far - the Exchange BCVs, having
lots & lots of
small files, cause the Storage Node to send a lot of
metadata to the
Networker server. But can't believe it could take down
the LAN.
Has anybody seen anything like this?
No, but you omitted some key information.
First off, what d exactly do you mean when you say your LAN is crashing?
Are your network managers able to sniff packets going into yor
NetWorker server?
What kind of hardware is involves (NetWorker server, Exchange client,
network cards, etc.)?
Which version of NetWorker (client and server)?
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
wit 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
|
