Mostrando postagens com marcador bpbkar. Mostrar todas as postagens
Mostrando postagens com marcador bpbkar. Mostrar todas as postagens

27 de jan. de 2010

How to benchmark the performance of the bpbkar process

A good way to determine the theoretical maximum read performance of the bpbkar daemon/process on the client is to run a dev null test. This test is usefully to isolate disk reads performances.

UNIX:
Create: /usr/openv/netbackup/logs/bpbkar directory and the /usr/openv/netbackup/bpbkar_path_tr touch file.

Run:
/usr/openv/netbackup/bin/bpbkar -nocont > /dev/null

example: /usr/openv/netbackup/bin/bpbkar -nocont /home > /dev/null

Note: Running this command will add I/O load to the system.
Before begin test change bpbkar log level to 5

The results can be found in the bpbkar log on the same client that the command was run from. It will give an idea ofhow quickly data is read from the file system being tested.

WINDOWS:
Create: \netbackup\logs\bpbkar folder
Run:
\netbackup\bin\bpbkar32 -nocont > NUL 2>

example: C:\program files\veritas\netbackup\bin\bpbkar32 -nocont E:\ > NUL 2> c:\temp.txt

Note: Running this command will add I/O load to the system.
Before begin test change bpbkar log level to 5

The results can be found in the bpbkar log on the same client that the command was run from. It will give an idea of how quickly data is read from the file system being tested.

http://seer.entsupport.symantec.com/docs/242918.htm

by TOCALS