If you ask EMC, I think they would recommend you increase the server
parallelism to at least 32... 
How long does it take to complete this group ? How much total data is
backed up on a typical group run ??
Do you have any restrictions on the tape drives regarding pools ??
You may be better off to post an excerpt of the rendered daemon.log
(with the names changed of course), from when the group starts to when
the group completes, so we can see what sessions overlapped, if any... I
would expect to initially see 4 sessions for each of the 3 drives for 12
concurrent sessions total in the beginning of the group run (you don't
say if there are tapes available to label and write to). But since you
only have a total of 23 save-sets to backup for the whole group... You
are not really coming close to loading the server to any significant
degree IMHO. We have 5 LTO-2 drives which are set to 7 target sessions
each, and it is not uncommon for us to see between 30 to 35 concurrent
sessions running. When our server is loaded like this, it's so busy,
attempting to do a remote-login to it is a waste of time as they almost
always time-out. And response on the NMC GUI is noticeably diminished...


> -----Original Message-----
> From: EMC NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of psoni
> Sent: Monday, May 04, 2009 2:10 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] Parallelism Question
> 
> I am running NW 7.3.3 on Win2K3 and would like to understand 
> how different parallelism settings work during backup.
> 
> I started a group manually and was monitoring its behaviour.
> 
> Here is an example:
> 
> Group has 3 clients
> # of savesets are 1 (client 1), 17 (client 2) and 5 (client 3).
> # of tape drives  = 4
> target sessions for the devices = 4
> max sessions = 512
> server parallelism = 16 ( 4 per device ) client parallelism = 
> 4 savegrp parallelism = 0 max parallelism (media pool ) = 0
> 
> There were three(3) tapes available (append) in that media 
> pool during backup and no other groups were running.
> 
> The savesets were backup up in the following order when I 
> kicked off the backup,
> 
> [1]   Four savesets (three from client 3, one from client 2)  
> to volume #1
> 
> [2]   Four savesets (one from client 1, two from client 2, 
> one from client 3)
>        to volume # 2
> 
> [3]   Only one saveset from client 2 to volume #3
> 
> 
> [4]   Eleven savesets ( eight from client 2, one from client 
> 3,  two indexes)
>         to volume # 2
>    
> [5]   Remaining five savesets from client 2 and it's index to 
> volume # 1.
>   
> 
> Is this the correct behaviour ? 
> I was expecting NW to run backup on more than one volume 
> simultaneously.
> 
> Thanks
> 
> +-------------------------------------------------------------
> ---------
> |This was sent by soni.parth AT gmail DOT com via Backup Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
> +-------------------------------------------------------------
> ---------
> 
> 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