BUG REPORT: After applying the NetBackup 6.5.2 release update, the client attribute "Maximum Data Streams" is ignored.

Problem

BUG REPORT: After applying the NetBackup 6.5.2 release update, the client attribute "Maximum Data Streams" is ignored.

Solution

Bug: 1293461

Detail:
The client attribute Maximum Data Streams is ignored in NetBackup 6.5.2.  It is overridden by the global value Maximum jobs per client.

To get the current value from the NetBackup GUI, navigate to Host Properties > Master Server > (select server) > Client Attributes > (select client) > General tab.  (Figure 1)

 

Background:
Maximum data streams:

The Maximum Data Streams property specifies the maximum number of jobs allowed at one time for each client selected in the Client Attributes host properties tab. (This value applies to the number of jobs on the client, even if multistreaming is not used.)

To change the setting, select Maximum Data Streams, then scroll to or enter a value up to 99.

Maximum Data Streams interacts with the Maximum Jobs per Client (Host Properties > Master Server > Global Attributes) and Limit Jobs Per Policy (a policy setting) as follows:
  • If Maximum Data Streams is not set, the limit is either Maximum Jobs Per Client or Limit Jobs Per Policy, whichever is lower.
  • If Maximum Data Streams is set, NetBackup ignores Maximum Jobs Per Client and uses either Maximum Data Streams or Limit Jobs Per Policy, whichever is lower.

This property appears for the clients of currently selected master servers only.

Troubleshooting:
In this example the client attribute value for Maximum Data Streams is set to 4.

The condition is seen in the NetBackup Resource Broker (nbrb - OID 118) log that indicates the value for NBU_CLIENT.MAXJOBS is set to max_ref_count=1.
7/4/2008 11:18:41.375 118 PID:1972 TID:4856 [CountedProvider::allocate] created and reserved resource sax.NBU_CLIENT.MAXJOBS.sax (current_ref_count=1, max_ref_count=1)

The correct value is displayed as max_ref_count=4.
7/4/2008 11:27:44.765 118 PID:4988 TID:4824 [CountedProvider::allocate] created and reserved resource sax.NBU_CLIENT.MAXJOBS.sax (current_ref_count=1, max_ref_count=4)

Note: Use bpclient command to determine the Maximum Data Streams value per client.
The value Maximum Data Streams is listed as Max Jobs This Client.

Example:
<install_path>\NetBackup\bin\admincmd>bpclient -client sax -L
Client Name: sax
Current Host:
       Hostname: sax
       IP Address: 0.0.0.0
Dynamic Address:       no
Free Browse:   Allow
List Restore:  Not Specified
Max Jobs This Client:  5
WOFB Enabled:  yes
WOFB FIM:      VSP
WOFB Usage:    Individual Drive Snapshot
WOFB Error Control:    Abort on Error
Connect options:       2 2 3

Workaround:
Change the value of Maximum jobs per client (Master Server Host Properties > Global Attributes > Maximum jobs per client) (Figure 2):

 

The Maximum jobs per client property specifies the maximum number of backup and archive jobs that NetBackup clients can perform concurrently. Default: 1 job.

If the workaround noted is not feasible, please apply the appropriate release update to resolve this issue.

ETA of Fix:
The formal resolution to this issue (Etrack 1293461) is included in the following patch release:
  • NetBackup 6.5 Release Update 3 (6.5.3)
This release is available at the support web site at:
 http://www.symantec.com/enterprise/support/downloads.jsp?pid=15143

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)