Group parallelism vs. Client parallelism 1

[backupworker]

What takes precedence when a backup is done, group or client parallelism?

We have a group set to a parallelism of 2, and the client in that group has its parallelism set to 4. When the backup starts, it only does 2 savestreams. Knowing this, I'm guessing the group takes precedence over the client, but then what is the point of being able to set parallelism on a client when it is always going to be overwritten by the group?

 

[yota38]

To keep a ratio between network & scsi,etc... bandwidth ?

 

[backupworker]

Huh?

 

[605]

The hierarchy is as follows:

Server Parallelism (# of streams in the data zone)
Savegroup Parallelism (since NW 6.1, # of streams per group)
Client Parallelism (# of streams per client)

Using "Savegroup Parallelism" makes only sense for overlapping groups.

If you do not set it (the default), then the first group could open an unlimited number of streams up to the "Server Parallelism" which means that no more stream 'will be available' for any new group that will be started while the first group one is still running.

 

[backupworker]

Thanks 605! Great explanation!