Veritas NetBackup™ Commands Reference Guide
- Introduction
- Appendix A. NetBackup Commands
- acsd
- add_media_server_on_clients
- backupdbtrace
- backuptrace
- bmrc
- bmrconfig
- bmrepadm
- bmrprep
- bmrs
- bmrsrtadm
- bp
- bparchive
- bpbackup
- bpbackupdb
- bpcatarc
- bpcatlist
- bpcatres
- bpcatrm
- bpcd
- bpchangeprimary
- bpclient
- bpclimagelist
- bpclntcmd
- bpclusterutil
- bpcompatd
- bpconfig
- bpdbjobs
- bpdbm
- bpdgclone
- bpdown
- bpduplicate
- bperror
- bpexpdate
- bpfis
- bpflist
- bpgetconfig
- bpgetdebuglog
- bpimage
- bpimagelist
- bpimmedia
- bpimport
- bpinst
- bpkeyfile
- bpkeyutil
- bplabel
- bplist
- bpmedia
- bpmedialist
- bpminlicense
- bpnbat
- bpnbaz
- bppficorr
- bpplcatdrinfo
- bpplclients
- bppldelete
- bpplinclude
- bpplinfo
- bppllist
- bpplsched
- bpplschedrep
- bppolicynew
- bpps
- bprd
- bprecover
- bprestore
- bpretlevel
- bpschedule
- bpschedulerep
- bpsetconfig
- bpstsinfo
- bpstuadd
- bpstudel
- bpstulist
- bpsturep
- bptestbpcd
- bptestnetconn
- bptpcinfo
- bpup
- bpverify
- cat_convert
- cat_export
- cat_import
- configurePorts
- create_nbdb
- csconfig cldinstance
- csconfig cldprovider
- csconfig meter
- csconfig throttle
- duplicatetrace
- importtrace
- jbpSA
- jnbSA
- ltid
- manageClientCerts
- mklogdir
- nbauditreport
- nbcatsync
- NBCC
- NBCCR
- nbcertcmd
- nbcertupdater
- nbcldutil
- nbcomponentupdate
- nbcplogs
- nbdb_admin
- nbdb_backup
- nbdb_move
- nbdb_ping
- nbdb_restore
- nbdb_unload
- nbdbms_start_server
- nbdbms_start_stop
- nbdc
- nbdecommission
- nbdelete
- nbdeployutil
- nbdevconfig
- nbdevquery
- nbdiscover
- nbdna
- nbemm
- nbemmcmd
- nbexecute
- nbfindfile
- nbfirescan
- nbftadm
- nbftconfig
- nbgetconfig
- nbhba
- nbholdutil
- nbhostidentity
- nbhostmgmt
- nbhypervtool
- nbjm
- nbkmsutil
- nboraadm
- nborair
- nbpem
- nbpemreq
- nbperfchk
- nbplupgrade
- nbrb
- nbrbutil
- nbregopsc
- nbreplicate
- nbrestorevm
- nbseccmd
- nbsetconfig
- nbsnapimport
- nbsnapreplicate
- nbsqladm
- nbstl
- nbstlutil
- nbstop
- nbsu
- nbsvrgrp
- resilient_clients
- restoretrace
- stopltid
- tl4d
- tl8d
- tl8cd
- tldd
- tldcd
- tlhd
- tlhcd
- tlmd
- tpautoconf
- tpclean
- tpconfig
- tpext
- tpreq
- tpunmount
- verifytrace
- vltadm
- vltcontainers
- vlteject
- vltinject
- vltoffsitemedia
- vltopmenu
- vltrun
- vmadd
- vmchange
- vmcheckxxx
- vmd
- vmdelete
- vmoprcmd
- vmphyinv
- vmpool
- vmquery
- vmrule
- vmupdate
- vnetd
- vxlogcfg
- vxlogmgr
- vxlogview
- W2KOption
Name
nbperfchk — measures a disk array's read and write speeds.
SYNOPSIS
-i inputpath -o outputpath [-s filesize] [-syncend] [-bs buffersize]
On UNIX systems, the directory path to this command is /usr/openv/netbackup/bin/support/
On Windows systems, the directory path to this command is install_path\NetBackup\bin\support\
DESCRIPTION
The nbperfchk command measures the read speed and write speed of a disk array. You can use this command to test the read speed and the write speed of the disks that host deduplicated data. For example, you can measure the speeds of the disks that host deduplicated data.
In a NetBackup media server deduplication pool (MSDP), use this command to measure the speed of the disks attached to the media server. The media server can be running any operating system that Veritas supports for media servers and MSDPs.
Note:
Veritas recommends that you work with a Veritas technical support staff member when you run this command and interpret its results. Veritas recommends a minimum disk performance level of 130 MB/sec for deduplicated read and write operations.
The nbperfchk utility enables you to write a test file to a disk, read back that test file, and observe the read speeds attained during the read operation. You can use the results from nbperfchk to make sure that the ReadBufferSize parameter is set appropriately in your backup environment. The ReadBufferSize parameter resides in the [CRDataStore] section of the contentrouter.cfg file. You can use this command as follows:
Use the following command to write data to the disks:
nbperfchk -i inputpath -o outputpath -s filesize -syncend
Use the following command to read data from the disks:
nbperfchk -i inputpath -o outputpath -bs buffersize
OPTIONS
- -i inputpath
For inputpath, specify the full path to an input file. The nbperfchk command reads this file and generates information about the read speed when this file is read to disk.
For example, you can specify the following to read in a file that contains all zero characters (0x00) from the /dev/zero:
- -o outputpath
For outputpath, specify the full path to an output file. The nbperfchk command creates this file.
For example, on writes, specify the path to the output file that you want to create. On reads, specify -o NULL to discard all the output as it is generated.
- -s filesize
For filesize, specify a file size that is equal to or larger than tha combined memory size of your computer plus the amount in the disk array. A file of this size ensures that the data is written to disk and not to a buffer.
- -syncend
The syncend parameter flushes the buffer and writes all data to disk.
- -bs buffersize
For buffersize, specify the read buffer size to use when nbperfchk runs. For example, 64k or 128k.
PROCEDURES
To analyze nbperfchk results and adjust the ReadBufferSize parameter setting
- Log in as the root user (UNIX) or the administrator (Windows) on the computer that hosts the content router.
In NetBackup environments, log into the media server.
- Change to a test directory.
- Type the nbperfchk command in the following format to write a large test file to the content router:
nbperfchk -i inputpath -o outputpath -s filesize -syncend
For example, the following command writes a 64 GB data file that contains all zeros to the e drive:
nbperfchk -i zero: -o e:\data1 -s 64g -syncend
- Type the nbperfchk command in the following format to read the test file and observe the read speeds in the nbperfchk output:
nbperfchk -i inputpath -o NULL -bs buffersize
Example 1. To observe several read speeds, with several buffer sizes, type the following series of commands:
nbperfchk -i e:\data1 -bs 64k -o NULL nbperfchk -i e:\data1 -bs 128k -o NULL nbperfchk -i e:\data1 -bs 256k -o NULL
Example 2. The following nbperfchk command reads back the data in file data1 and uses a buffer size of 1024 K:
C:\Users\administrator.mymediaserver\Desktop>nbperfchk -i e:\data1 -bs 1024k -o NULL 195 MB @ 65.3 MB/sec, 194 MB @ 64.9 MB/sec 295 MB @ 49.4 MB/sec, 100 MB @ 33.5 MB/sec 403 MB @ 44.8 MB/sec, 108 MB @ 35.8 MB/sec 505 MB @ 42.1 MB/sec, 102 MB @ 34.1 MB/sec 599 MB @ 40.0 MB/sec, 94 MB @ 31.3 MB/sec 705 MB @ 39.2 MB/sec, 106 MB @ 35.5 MB/sec 821 MB @ 39.2 MB/sec, 116 MB @ 38.8 MB/sec 943 MB @ 39.4 MB/sec, 122 MB @ 40.8 MB/sec 1024 MB @ 40.1 MB/secObserve the following when you analyze the data:
The left two columns show the amount of data read and the average read speed.
The final line shows the overall read speed. This is the most important line in this output because it shows you how fast the total read occurred with the buffer size you specified.
The right two columns show the average read speed in the last 3 seconds of each read. Unless these numbers vary drastically from read to read, you can disregard the right two columns.
- Analyze your read speeds and adjust the ReadBufferSize parameter if necessary.
Your operating system, your disk speeds, and the ReadBufferSize parameter setting all affect restore and rehydration performance.
Veritas recommends that you type several nbperfchk commands and increase the size of the argument to the -bs parameter each time. Example 1 in step 4 shows this method. If you can enter ever-increasing arguments to the -bs parameter, you can probably increase the size of the ReadBufferSize parameter in the [CRDataStore] section of the contentrouter.cfg file.
By default, ReadBufferSize=65536, which is 64K. Veritas testing shows that ReadBufferSize=1048576, which is 1024 X 1024, or 1M, offers good performance on most Windows systems. On most UNIX systems, Veritas testing shows that ReadBufferSize=65536 (the default) offers good performance.
For information about how to edit NetBackup configuration files, see the NetBackup documentation.