Hi All,
Other than server parallelism and target session, there is client parallelism.
Have you guys happen to know the correct behaviour of the client parallelism

What I have observe in my environment
client parallelism = 8
target session = 4
server parallelism = 48
jukebox parallelism -> n/a (version 6.0.3)

The first backup will take 2 drive
If I start the second backup, it will grab another 2 drive.
So total output from this client will be 16 streams (4 drive)
Is this correct to assume that client parallelism is not global parameter
but more on savegroup level.

any comment?

cheers - han

At 8/23/2002 09:08 AM, Rymwid, Peter wrote:

Hi Mathew,
Good answer, but how do you implement parallelism factor on jukebox into
this picture?

Peter Rymwid

-----Original Message-----
From: Matthew Bourne [mailto:mbourne2001 AT LYCOS.CO DOT UK]
Sent: Friday, August 23, 2002 7:40 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] target sessions


Hi,

How many savesets are there in your 375GB backup ?

The server parallelism sets a limit on the number of concurrent savesets
occurring at any given point - so if you have a parallelism value of 16,
your backup server can write up to 16 different savesets continuously.

Assuming that you have enough savesets to fill this capacity, and that all 8
of your drives are used for the backup, you might only be writing 2 savesets
per drive.

The other factor to consider here is the target sessions value for each of
your drives.  I have found that my DLT7000 drives yield the best streaming
rate when they are writing 6 savesets each - having 2 of these drives, I
have set the server parallelism to a value of 12, and the target sessions
for each drive to a value of 6.

The point is, it doesn't matter how large you set the target sessions
parameter for each of your drives - if your server parallelism isn't large
enough to use those target sessions then your backups may be running at less
than optimum speed.

Regards,

Matthew

--
Note: To sign off this list, send a "signoff" 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" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

cheers - han

--
Note: To sign off this list, send a "signoff" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=