A possible solution is to disable index saves as part of every group and setup 
a cron job separately (using savegroup -O, if I remember right) to do the index 
save.

----
Matthew Huff       | One Manhattanville Rd
OTA Management LLC | Purchase, NY 10577
http://www.ox.com ; | Phone: 914-460-4039
aim: matthewbhuff  | Fax:   914-460-4139

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Khan, Sami
Sent: Friday, August 14, 2009 4:21 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Revisiting the case of hung savegroups

Greetings,

Posting this again, I have read through the list entries, and tried tweaking 
client/group parallelism in reasonably possible ways. But, this morning again 
all savegroups were "hung" waiting to write indices. 

Reverse and forward dns lookups work, not too many clients (around 100) and 
less than 10 groups, client parallelism values are minimum 4. We have upgraded 
from 7.2.2 to 7.4.4 (both Windows 2003) last month and this problem has been 
recurring once or twice a week since then. 

Is there a way to tell Networker to go on writing other indices if one 
client/group hangs? Any advice will be greatly appreciated!

Thanks,
Sami

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