Hello,
I can only offer suggestions, try them
If this large clients are failing repeatedly on full backups you may want 
to consider any of this options, in no particular order, one at a time.
1. Set Group Time-out to zero.
2. Try using higher version of client if everything else fails to produce 
result & make sure you test recover.
3. Can you try and spit up your "Full" backups on different schedule ?
4. Could you use Disk\VTL for backups ? Dedupe appliance ?
5. Is there any tune-ups ( memory, CPU, GB NIC) be applied on this problem 
clients ?
6. Could you not exclude index backup, since the failure seems to occur 
with it & schedule a separate savegrp -O " Group Name"  for Index backup 
7. Could some of this larger client be converted to Storage Nodes ?




"Clark, Patti" <clarkp AT OSTI DOT GOV> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
06/10/2008 12:28 PM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond 
to
"Clark, Patti" <clarkp AT OSTI DOT GOV>


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
[Networker] Some larger file system backups failing






RHEL4 x86_64 host, v7.3.3 32-bit Networker server, Quantum M2500 library
w/LTO-2 drives.  Affected clients are a mix of Solaris and RHEL4 all
v7.3.3.

My full backups ran over the weekend.  I had 4 or 5 clients fail to back
up some of their larger file systems, anywhere between 14GB and 190GB in
size.  I've been making manual attempts at the specific file systems
with some successes and the rest continuing to fail.  One example is
35GB of data, the backup streams just fine, seemingly reaches the end,
and instead of closing the saveset and writing the index, networker
indicates in the server daemon.log that it had "lost connection to
server, exiting".  It will make the 2nd attempt allowed by the
configuration and basically repeat with the same results.  I've
restarted networker on both the server and the particular clients
without any improvement.  Last night all of the incrementals ran
successfully.  I've had similar issues in the past with Win clients, but
I received a patched nsrexecd from EMC which resolved that problem.

I don't see where tweaking anything on Networker short of breaking up
the file systems into multiple savesets will help >:-P.  It is not
really timing out and firewalls are not involved - I have nics on each
subnet and no storage nodes.  <sigh>

I hesitate to upgrade to another version since the discussions here
haven't sold me on going to 7.4, yet.  Any ideas?  Is 7.4 worth going to
or am I just trading one set of networker blues for another (different
is not better).


Patti Clark
Sr. Unix System Administrator - RHCT, GSEC
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



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