Video Screencast Help

Activity Monitor: Five days ago?

Created: 20 Jun 2012 • Updated: 20 Jun 2012 | 9 comments
This issue has been solved. See solution.


basically i'm looking to calculate the size of data being backup up from the Full Backup schedules, five or six days ago. The activity monitor does not show it by default. And I failed to find a parameter to change to show backup jobs older than 5 days.

So, I tried the command line. but got lost with the output of (bpdbjobs -all_columns -report). I couldn't find whats the field number that shows the 'start time' and 'kilobytes'. Reading the manpage didn't help really. I'm a little experienced with the command line so if i know these two fields and the seperator/delimiter of the output report, I can finish the job and add up the numbers in one command or so.

My my question is: 

1- how to get the activity monitor to show older jobs details


2- what are the field numbers that correspond to 'start time', 'kilobytes', and seperator

thanks, and please tolerate my lengthy, yet easy request :)

Discussion Filed Under:

Comments 9 CommentsJump to latest comment

Marianne's picture

I believe all your questions will be answered in this TN:

1. bpdbjobs -clean -keep_days days

2.  -all_columns
Displays all columns of a report or summary. Some of the more useful fields of this command are:

field2 = jobtype
0=backup, 1=archive, 2=restore, 3=verify, 4=duplicate, 5=import, 6=catalog backup, 7=vault, 8=label, 9=erase, 10=tape request, 11=tape clean, 12=format tape, 13=physical inventory, 14=qualification, 15=database recovery, 16=media contents, 17=image delete, 18=LiveUpdate

field3 = state
0=queued, 1=active, 2=wait for retry, 3=done, 4=suspended, 5=incomplete

field5 = policy
The policy that this job is associated with.

field6 = schedule
The schedule that this job is associated with.

field14 = operation
4=vault initialize
5=vault duplication
6=vault duplication complete
7=vault catalog backup
8=vault eject and report
9=vault complete

field21 = subtype
0=immediate, 1=scheduled, 2=user-initiated, 3=quick erase, 4=long erase, 5=database backup staging, 6=database backup cold

field23 = schedule_type
0=full, 1=incr, 2=user backup, 3=user archive, 4=cumulative-incr

field24 = priority

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Andy Welburn's picture

I wouldn't mind but I have *this* book-marked: blush

How to manually adjust the number of days a backup job's history remains available in the job activity monitor


How to manually adjust the number of days a backup job's history remains available in the job activity monitor


To adjust this, use the bpdbjobs command (found in the /usr/openv/netbackup/bin/admincmd/ directory) as shown below:
bpdbjobs -clean -keep_days <number_of_days>
For instance, to set it for seven days, use the following command:
# /usr/openv/netbackup/bin/admincmd/bpdbjobs -clean -keep_days 7
Andy Welburn's picture

1. Possible:

You can either amend registry or use bpsetconfig (can use latter for WIn or *nix) to amend the values of KEEP_JOBS_SUCCESSFUL_HOURS and KEEP_JOBS_HOURS from their default 78


2. This may help:

DOCUMENTATION: In NetBackup 6.x and 7.x, what does the output of "bpdbjobs -most_columns" mean?

or you could look at using bpimagelist (can be run using a *lot* of different search parameters):

DOCUMENTATION: What are the different fields in "bpimagelist -l" output?

YDardeer's picture

Thanks. The most_columns option has it. So starting_time/date is field#9. and the size is field#15. But what is the delimeter? is it 'comma'? 

YDardeer's picture

Thanks. The field ordering is not quite as the document state (well, not all of them). but i can figure it out. the kilobytes field is correct at field#15.

but i can't seem to understand the start time/date format, assuming it is correct at field#9. 

this example

 #bpdbjobs -most_columns -report | awk -F',' '{print $1, $9, $15}'

((output should be jobID, started, kilos))

149685 1340136014 361728
149684 1340136014 6912
149683 1340136019 327744
149682 1340136013 288
149681 1340136000
149680 1340136000
149679 1340136000
149678 1340136000 49839
149677 1340136000
149676 1340128949
149675 1340128808 244572
149674 1340128800
149673 1340124205
149672 1340123676 3008832
149671 1340123628 1344
149670 1340122572 15093088
Andy Welburn's picture

Use bpdbm -ctime ctime to convert


# bpdbm -ctime 1340136000
1340136000 = Tue Jun 19 21:00:00 2012

Andy Welburn's picture

Just to confirm you really want to use bpdbjobs for this exercise?

bpdbjobs is only going from what's in the Activity Monitor (or vice versa!).

Field 9 is the time the job was first queued so not useful unless that's what you really want (could queue for hours before actually starting).

Not sure about the solution you've marked - just essentially para-phrasing what Marianne posted & at the same time highlighting my own lapse(s) in memory (it's an age thing apparently!)