09-27-2016 08:31 AM
NBU 7.6.0.3
i've been asked to test the disk/path where images are stored prior to dedup. just want to know how long will this command run:
./bpbkar -nocont -dt 0 -nofileinfo -nokeepalives /YOUR-DATA-PATH-TO-TEST-HERE > /dev/null
do i leave it running overnight or wait for it to finish?
there isn't a man page for NBU commands so it's hard to tell what each switch does also.
Solved! Go to Solution.
09-27-2016 07:23 PM
To check this "bpbkar -nocont..." progress, you can either look at the bpbkar logs (to see if it keeps reading the files you point to).
How long it will run really depends on how big your path is, try a smaller one first and you probably can estimate on your own.
09-27-2016 09:34 AM
"images are stored prior to dedup", could you expline this.. what is this path contains.. source data that requried to be backup., or backup images that are being backup with disk STU(non dedup disk)
this commend time depends on type of data & number of files.....unless we know what kind of data the path you are looking to check contaings its hard to answer...
09-27-2016 10:20 AM
Who asked you to run this command, and why can't you ask them for clarification? Since bpbkar is not in the command reference manual, I think that means it's not intended for general CLI usage.
I can't answer "How long will this run?", but I can contribute a little bit about what the options mean:
First, you must be on some version of Unix or Linux, because the command would be bpbkar32 on Windows.
Usually, bpbkar is started by another NetBackup process. The -nocont parameter has an effect of inhibiting the return of status to the calling process. The calling process expects a minimum of a "BACKUP START" message as well as an exit status. You would expect catalog messages, too, in a real backup.
In reverse, bpbkar expects a "CONTINUE BACKUP" message from the calling process. With the -nocont option, it doesn't look for it.
The -nokeepalives option inhibits the sending of periodic 1-byte keepalive message to the calling process, which would otherwise time out after a few minutes.
09-27-2016 12:05 PM - edited 09-27-2016 12:13 PM
09-27-2016 07:23 PM
To check this "bpbkar -nocont..." progress, you can either look at the bpbkar logs (to see if it keeps reading the files you point to).
How long it will run really depends on how big your path is, try a smaller one first and you probably can estimate on your own.
10-10-2016 11:55 PM
10-11-2016 03:42 AM