cancel
Showing results for 
Search instead for 
Did you mean: 

bpbkar32 produce high cpu usage on client

Holger_Luebbers
Level 4
Hi !

Problem :

Backup job produce 100% cpu-usage on any windows-clients ( Server 2003 Standard Edition ) , work on this client is not possible, other processes are not possible.

Backupserver is a sun Ultra 60 with solaris 8, Netbackup 5.1 MP4

Thanks in advance

Greets
Holger
4 REPLIES 4

Stumpr2
Level 6
Methods to improve backup performance without adjusting VERITAS NetBackup (tm) buffer files
http://support.veritas.com/docs/260719

Details:
Modify or adjust the following settings individually or collectively. Each point may not apply to every NetBackup environment.

Modifications within NetBackup:
-Disable all NetBackup logging.

-Disable Compression in the Policy Attributes. (Conversely enable Compression. The point is, you don't want to have both software compression and hardware compression active simultaneously.)

-Disable intelligent disaster recovery (IDR) and true image restore (TIR) in the Policy Attributes. (NetBackup will spend extra cycles on these activities thereby causing the backup to last longer.)

-Disable Open Transaction Manager (OTM) and Volume Snapshot Provider (VSP). OTM and VSP will cause backups to last longer.

-If disabling OTM or VSP is not an option, consider moving the OTM or VSP cache file to a different drive letter. (If backing up the C:\ drive, locate the cache file on D:\ or vice versa.)

-Disable Job Tracker on each client machine. In NetBackup 4.5 and earlier, this can be done by removing it from the All Users Startup Group and killing the active process. In NetBackup 5.0 tracker starts through the registry. See TechNote 267253 on how to disable tracker in NetBackup 5.0. (Job Tracker is listed as tracker.exe in Task Manager. Job Tracker is designed for computers that are used as desktop workstations, to tell the users when a backup is active on their workstation. Consequently it is not needed on normal data center class servers.)

-In the Policy, change from using the directive "All Local Drives" to individual drive letters and system state. (In many situations, specifying drive letters produces quicker backups than using the All Local Drives directive.)

-Examine Exclude and Include Lists and eliminate them if possible. (NetBackup must process each of these lists and this will slow down the backup.)

Modifications Outside of NetBackup:
-Disable outbound Virus Scanning on all data sets being backed up

-Disable NT File System (NTFS) compression on all data sets being backed up

-Ensure that network communication is working optimally:

1. Verify that the network interface card's (NIC's) Hub/Switch ports are set to Fixed Duplexing and Fixed Speed rather then Auto-sense and Auto-negotiate.
2. Use FTP to transfer a large file (50 megabytes or more) from the media server to the client and back again. Time each operation. If moving the file in either direction is significantly longer then the other, there is a network problem.


-Try using Host files rather then relying on the domain name server (DNS) for name resolution (use extreme caution if doing this).

-Connect the tape drives onto different SCSI buses. For example: Assume 8 tape drives, 2 drives connected to each SCSI card requiring 4 total SCSI cards.

h_m
Level 6
Check documentation to ensure you have the minimun CPU and memory spec and O/S for the client.

AKopel
Level 6
Both of those answers are good..
Another thing to add/clarify.
1) What is the CPU/memory on your client
2) Do you have multiple data streams enabled (which will cause multiple instances of bpbkar)

In my experience, Multiple data streams and client compression are the biggest hits to CPU in regards to NBU.

Aaron

Dennis_Strom
Level 6
This patch provides fixes to the NetBackup Windows NT/2000 server ...
for the bpbkar process shows that the pathname containing the Swedish ... sluggish and unresponsive, due to high CPU usage by the winlogon.exe. process. ...
support.veritas.com/docs/234924