HI,
I think you should create a separate policy for the newer clients (you can copy exisiting) and set more streams in the policy backup selection list of this new policy.

At the same time 'Jobs per client' attribute on master to be set to (No.of streams per client for newer clients).

Original policy remains same if you have only 2 streams in backup selection list. In case you have more than 2 streams in here you can use 'Limit Jobs per Policy'.

Everybody correct me if I am wrong.

Br,
Deepak.

>Is there a way to get around the global setting on the Master
NO - you will have to increase this parameter. All other job limiting parameters are still limited to this value. This sets the highest available limit. If it is set at 2 then any value in the other parameters will likewise be limited to 2.

From the sysadmin guide:

The number of streams that can run concurrently for a policy or client is determined by the following:
◆ Storage unit and schedule multiplexing limit
◆ Number of drives that are available
◆ Maximum concurrent jobs settings for the policy and client
Each storage unit and each schedule has a maximum multiplex setting. The lower of the two settings is the limit for a specific schedule and storage unit. The maximum number of streams that can be multiplexed is limited to the sum of the multiplexing limits for all drives available in the storage unit and schedule combinations.
For example, assume there are two storage units with one drive in each. MPX on storage unit 1 is set to 3 and MPX on storage unit 2 is set to 5. If MPX is set to 5 or greater in the schedules, then 8 streams can run concurrently.
The maximum jobs settings also limit the maximum number of streams:
◆ Maximum Jobs Per Client (Host Properties > Master Server > Global NetBackup
Attributes)
◆ Limit jobs per policy (policy attribute)
◆ Maximum Data Streams (Set the number in Host Properties > Master Server >
Client Attributes)
The maximum job settings are interdependent as follows:
◆ If Maximum Data Streams is not set, the lowest value of Maximum Jobs Per Client and Limit Jobs Per Policy is the limiting factor.
◆ If Maximum Data Streams is set, then NetBackup ignores Maximum Jobs Per Client and uses the lowest value of Maximum Data Streams and Limit Jobs Per Policy as the limiting factor.

This is the second time I attempted to post this reply. The source is the sysadmin guide.

Setting the Number of Streams That Can Run Concurrentl

The number of streams that can run concurrently for a policy or client is determined by the following:
◆ Storage unit and schedule multiplexing limit
◆ Number of drives that are available
◆ Maximum concurrent jobs settings for the policy and client Each storage unit and each schedule has a maximum multiplex setting. The lower of the two settings is the limit for a specific schedule and storage unit. The maximum number of streams that can be multiplexed is limited to the sum of the multiplexing limits for all drives available in the storage unit and schedule combinations. For example, assume there are two storage units with one drive in each. MPX on storage unit 1 is set to 3 and MPX on storage unit 2 is set to 5. If MPX is set to 5 or greater in the schedules, then 8 streams can run concurrently. The maximum jobs settings also limit the maximum number of streams:
◆ Maximum Jobs Per Client (Host Properties > Master Server > Global NetBackup Attributes)
◆ Limit jobs per policy
◆ Maximum Data Streams (Set the number in Host Properties > Master Server > Client Attributes) The maximum job settings are interdependent as follows:
◆ If Maximum Data Streams is not set, the lowest value of Maximum Jobs Per Client and Limit Jobs Per Policy is the limiting factor.
◆ If Maximum Data Streams is set, then NetBackup ignores Maximum Jobs Per Client and uses the lowest value of Maximum Data Streams and Limit Jobs Per Policy as the limiting factor.

As always, Bob always going above and beyond for the answer. Not always the answer I want to hear but always the right answer. It sounds like I can do some tweaking and up the Max while still keeping the slower clients down to 2 by using some of the other limitations.

Thank you all for your responses. Don't go away, I'm sure I'll have more questions soon.

Randy

I have a few SAN attach clients and a few other Lan based clients for backup on my network. Currently using NBU 6.5.4 as the backup tool. The global settings for ' Max jobs per client' is set to 3. While I want to maintain 3 streams for Lan based clients, I want to increase this to 6 for SAN attach clients. Since the Max jobs per client is a global setting, I intend to implement this as follows. Pls confirm if this is the correct way.

1. Set the 'Max jobs per client' in the Global attributes section of the master server to 6
2. Go to the Client attributes of each of the LAN based client and set the ' MAX DATA STREAMS' to 3
3. Enable the 'Allow multiple data streams' in the policy

Will this force the LAN based clients to run with 3 streams max while the SAN attach clients run at a max of 6 streams concurrently ?

Are there any other methods of implementing this ?

Thanks in advance
Nash