bpdbjobs !! - Veritas Net Backup

This is a discussion on bpdbjobs !! - Veritas Net Backup ; Kelly, thanks a lot for this information but you know, this JOB: bpdbjobs -header -report -all_columns with this i can't see the header and why ? jobid,jobtype,state,etc... Kelly Wyatt a écrit : > This is what I got from VERITAS ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: bpdbjobs !!

  1. bpdbjobs !!

    Kelly, thanks a lot for this information but you know, this JOB:

    bpdbjobs -header -report -all_columns

    with this i can't see the header and why ?

    jobid,jobtype,state,etc...


    Kelly Wyatt a écrit :

    > This is what I got from VERITAS support... I have to figure out what

    some of
    > the fields mean (like jobtype -- a numeric -- what is a backup, a
    > restore...). Below you will see a sample record from my output and

    the
    > fields that I determined went with them.
    >
    > jobid 305
    > jobtype 0
    > state 3
    > status 1
    > class a.unix
    > schedule full
    > client asrv01
    > server aback.unx
    > started 0950916985
    > elapsed 0000011093
    > ended 0950928078
    > stunit a.pc
    > try 1
    > operation ?
    > kbytes 21022930
    > files 416421
    > pathlastwritten ?
    > percent ?
    > jobpid 12944
    > owner root
    > subtype 1
    > classtype 0
    > scheduletype 0
    > priority 0
    > group ?
    > masterserver aback
    > retention units 3
    > retentionperiod 2
    > compression 0
    > kbyteslastwritt 0
    > fileslastwritt 0
    > filelistcount 1
    > files ALL_LOCAL_DRIVES
    > trycount 1
    > trypid 12944
    > trystunit a.pc
    > tryserver aback.unx
    > trystarted 950916985
    > tryelapsed 11093
    > tryended 950928078
    > trystatus 1
    > trystatusdesc the requested operation was partially successful
    > trystatuscount 28
    > trystatuslines 02/18/00 18:36:31 - mounting AU0050
    > 02/18/00 18:36:32 - connecting
    > 02/18/00 18:36:33 - connected; connect time: 000:00:01
    > 02/18/00 19:17:36 - mounted; mount time: 000:41:05
    > 02/18/00 19:17:36 - positioning to file 1
    > 02/18/00 19:18:02 - positioned; position time: 000:00:26
    > 02/18/00 19:18:02 - begin writing
    > 02/18/00 19:32:14 - positioning to file 2
    > 02/18/00 19:32:14 - positioned; position time: 000:00:00
    > 02/18/00 19:41:45 - positioning to file 3
    > 02/18/00 19:41:45 - positioned; position time: 000:00:00
    > 02/18/00 19:52:12 - positioning to file 4
    > 02/18/00 19:52:12 - positioned; position time: 000:00:00
    > 02/18/00 20:01:46 - positioning to file 5
    > 02/18/00 20:01:46 - positioned; position time: 000:00:00
    > 02/18/00 20:10:10 - positioning to file 6
    > 02/18/00 20:10:10 - positioned; position time: 000:00:00
    > 02/18/00 20:18:48 - positioning to file 7
    > 02/18/00 20:18:48 - positioned; position time: 000:00:00
    > 02/18/00 20:32:53 - positioning to file 8
    > 02/18/00 20:32:53 - positioned; position time: 000:00:00
    > 02/18/00 20:47:59 - positioning to file 9
    > 02/18/00 20:47:59 - positioned; position time: 000:00:00
    > 02/18/00 21:03:58 - positioning to file 10
    > 02/18/00 21:03:58 - positioned; position time: 000:00:00
    > 02/18/00 21:23:42 - positioning to file 11
    > 02/18/00 21:23:42 - positioned; position time: 000:00:00
    > 02/18/00 21:41:03 - end writing; write time: 002:23:01
    > trybyteswritten 21022930
    > tryfileswritten 416421
    >
    > I believe you can send a parameter like hoursago or something to get a


    > certain time period. Here at SAS, we put the output to a SAS dataset

    daily
    > and use SAS to process the data. We also have the following in ous
    > job.conf:
    >
    > KEEP_DAYS 10
    > KEEP_SUCCESSFUL_DAYS 5
    >
    > By putting the data to a dataset daily and trimming the job

    information as
    > we do, the job monitor comes up much more quickly and the jobs data

    does not
    > get so large.
    >
    > Kelly
    > antilles89 wrote in message
    > news:394FEC6A.B70F363@wanadoo.fr...
    > > /usr/openv/netbackup/bin/admincmd/bpdbjobs -report -all_columns
    > >
    > > The result of this is very interessant but i don't know the name of
    > > this columns and should i change the columns separate "," to ";" or

    TAB
    > > or
    > > other character.
    > >
    > > And finally if it possible to get an executing period : one month

    for
    > > example.
    > >
    > >





  2. Re: bpdbjobs !!


    antilles89 wrote:
    >Kelly, thanks a lot for this information but you know, this JOB:
    >
    >bpdbjobs -header -report -all_columns
    >
    >with this i can't see the header and why ?
    >
    >jobid,jobtype,state,etc...
    >
    >
    >Kelly Wyatt a écrit :
    >
    >> This is what I got from VERITAS support... I have to figure out what

    >some of
    >> the fields mean (like jobtype -- a numeric -- what is a backup, a
    >> restore...). Below you will see a sample record from my output and

    >the
    >> fields that I determined went with them.
    >>
    >> jobid 305
    >> jobtype 0
    >> state 3
    >> status 1
    >> class a.unix
    >> schedule full
    >> client asrv01
    >> server aback.unx
    >> started 0950916985
    >> elapsed 0000011093
    >> ended 0950928078
    >> stunit a.pc
    >> try 1
    >> operation ?
    >> kbytes 21022930
    >> files 416421
    >> pathlastwritten ?
    >> percent ?
    >> jobpid 12944
    >> owner root
    >> subtype 1
    >> classtype 0
    >> scheduletype 0
    >> priority 0
    >> group ?
    >> masterserver aback
    >> retention units 3
    >> retentionperiod 2
    >> compression 0
    >> kbyteslastwritt 0
    >> fileslastwritt 0
    >> filelistcount 1
    >> files ALL_LOCAL_DRIVES
    >> trycount 1
    >> trypid 12944
    >> trystunit a.pc
    >> tryserver aback.unx
    >> trystarted 950916985
    >> tryelapsed 11093
    >> tryended 950928078
    >> trystatus 1
    >> trystatusdesc the requested operation was partially successful
    >> trystatuscount 28
    >> trystatuslines 02/18/00 18:36:31 - mounting AU0050
    >> 02/18/00 18:36:32 - connecting
    >> 02/18/00 18:36:33 - connected; connect time: 000:00:01
    >> 02/18/00 19:17:36 - mounted; mount time: 000:41:05
    >> 02/18/00 19:17:36 - positioning to file 1
    >> 02/18/00 19:18:02 - positioned; position time: 000:00:26
    >> 02/18/00 19:18:02 - begin writing
    >> 02/18/00 19:32:14 - positioning to file 2
    >> 02/18/00 19:32:14 - positioned; position time: 000:00:00
    >> 02/18/00 19:41:45 - positioning to file 3
    >> 02/18/00 19:41:45 - positioned; position time: 000:00:00
    >> 02/18/00 19:52:12 - positioning to file 4
    >> 02/18/00 19:52:12 - positioned; position time: 000:00:00
    >> 02/18/00 20:01:46 - positioning to file 5
    >> 02/18/00 20:01:46 - positioned; position time: 000:00:00
    >> 02/18/00 20:10:10 - positioning to file 6
    >> 02/18/00 20:10:10 - positioned; position time: 000:00:00
    >> 02/18/00 20:18:48 - positioning to file 7
    >> 02/18/00 20:18:48 - positioned; position time: 000:00:00
    >> 02/18/00 20:32:53 - positioning to file 8
    >> 02/18/00 20:32:53 - positioned; position time: 000:00:00
    >> 02/18/00 20:47:59 - positioning to file 9
    >> 02/18/00 20:47:59 - positioned; position time: 000:00:00
    >> 02/18/00 21:03:58 - positioning to file 10
    >> 02/18/00 21:03:58 - positioned; position time: 000:00:00
    >> 02/18/00 21:23:42 - positioning to file 11
    >> 02/18/00 21:23:42 - positioned; position time: 000:00:00
    >> 02/18/00 21:41:03 - end writing; write time: 002:23:01
    >> trybyteswritten 21022930
    >> tryfileswritten 416421
    >>
    >> I believe you can send a parameter like hoursago or something to get a

    >
    >> certain time period. Here at SAS, we put the output to a SAS dataset

    >daily
    >> and use SAS to process the data. We also have the following in ous
    >> job.conf:
    >>
    >> KEEP_DAYS 10
    >> KEEP_SUCCESSFUL_DAYS 5
    >>
    >> By putting the data to a dataset daily and trimming the job

    >information as
    >> we do, the job monitor comes up much more quickly and the jobs data

    >does not
    >> get so large.
    >>
    >> Kelly
    >> antilles89 wrote in message
    >> news:394FEC6A.B70F363@wanadoo.fr...
    >> > /usr/openv/netbackup/bin/admincmd/bpdbjobs -report -all_columns
    >> >
    >> > The result of this is very interessant but i don't know the name of
    >> > this columns and should i change the columns separate "," to ";" or

    >TAB
    >> > or
    >> > other character.
    >> >
    >> > And finally if it possible to get an executing period : one month

    >for
    >> > example.
    >> >
    >> >

    >
    >
    >



    Not sure if this is quite what you want, I don't have the need to report
    on all those thousands of fields. I just use bpdbjobs -report. This has no
    column headings, so [very basic kludge] - i created a text file with the
    headings manually setup, then run a script to add the bpdbjobs -report on
    to the end. Somehow i think this is too simple for what you're asking ??.


  3. Re: bpdbjobs !!


    Does anyone know how to get the start/elapsed/end times into a readable format
    rather than the epoch format? This is new to 4.5 bpdbjobs as far as I can
    tell.

    thanks,
    Jim


    "Creaky" wrote:
    >
    >antilles89 wrote:
    >>Kelly, thanks a lot for this information but you know, this JOB:
    >>
    >>bpdbjobs -header -report -all_columns
    >>
    >>with this i can't see the header and why ?
    >>
    >>jobid,jobtype,state,etc...
    >>
    >>
    >>Kelly Wyatt a écrit :
    >>
    >>> This is what I got from VERITAS support... I have to figure out what

    >>some of
    >>> the fields mean (like jobtype -- a numeric -- what is a backup, a
    >>> restore...). Below you will see a sample record from my output and

    >>the
    >>> fields that I determined went with them.
    >>>
    >>> jobid 305
    >>> jobtype 0
    >>> state 3
    >>> status 1
    >>> class a.unix
    >>> schedule full
    >>> client asrv01
    >>> server aback.unx
    >>> started 0950916985
    >>> elapsed 0000011093
    >>> ended 0950928078
    >>> stunit a.pc
    >>> try 1
    >>> operation ?
    >>> kbytes 21022930
    >>> files 416421
    >>> pathlastwritten ?
    >>> percent ?
    >>> jobpid 12944
    >>> owner root
    >>> subtype 1
    >>> classtype 0
    >>> scheduletype 0
    >>> priority 0
    >>> group ?
    >>> masterserver aback
    >>> retention units 3
    >>> retentionperiod 2
    >>> compression 0
    >>> kbyteslastwritt 0
    >>> fileslastwritt 0
    >>> filelistcount 1
    >>> files ALL_LOCAL_DRIVES
    >>> trycount 1
    >>> trypid 12944
    >>> trystunit a.pc
    >>> tryserver aback.unx
    >>> trystarted 950916985
    >>> tryelapsed 11093
    >>> tryended 950928078
    >>> trystatus 1
    >>> trystatusdesc the requested operation was partially successful
    >>> trystatuscount 28
    >>> trystatuslines 02/18/00 18:36:31 - mounting AU0050
    >>> 02/18/00 18:36:32 - connecting
    >>> 02/18/00 18:36:33 - connected; connect time: 000:00:01
    >>> 02/18/00 19:17:36 - mounted; mount time: 000:41:05
    >>> 02/18/00 19:17:36 - positioning to file 1
    >>> 02/18/00 19:18:02 - positioned; position time: 000:00:26
    >>> 02/18/00 19:18:02 - begin writing
    >>> 02/18/00 19:32:14 - positioning to file 2
    >>> 02/18/00 19:32:14 - positioned; position time: 000:00:00
    >>> 02/18/00 19:41:45 - positioning to file 3
    >>> 02/18/00 19:41:45 - positioned; position time: 000:00:00
    >>> 02/18/00 19:52:12 - positioning to file 4
    >>> 02/18/00 19:52:12 - positioned; position time: 000:00:00
    >>> 02/18/00 20:01:46 - positioning to file 5
    >>> 02/18/00 20:01:46 - positioned; position time: 000:00:00
    >>> 02/18/00 20:10:10 - positioning to file 6
    >>> 02/18/00 20:10:10 - positioned; position time: 000:00:00
    >>> 02/18/00 20:18:48 - positioning to file 7
    >>> 02/18/00 20:18:48 - positioned; position time: 000:00:00
    >>> 02/18/00 20:32:53 - positioning to file 8
    >>> 02/18/00 20:32:53 - positioned; position time: 000:00:00
    >>> 02/18/00 20:47:59 - positioning to file 9
    >>> 02/18/00 20:47:59 - positioned; position time: 000:00:00
    >>> 02/18/00 21:03:58 - positioning to file 10
    >>> 02/18/00 21:03:58 - positioned; position time: 000:00:00
    >>> 02/18/00 21:23:42 - positioning to file 11
    >>> 02/18/00 21:23:42 - positioned; position time: 000:00:00
    >>> 02/18/00 21:41:03 - end writing; write time: 002:23:01
    >>> trybyteswritten 21022930
    >>> tryfileswritten 416421
    >>>
    >>> I believe you can send a parameter like hoursago or something to get

    a
    >>
    >>> certain time period. Here at SAS, we put the output to a SAS dataset

    >>daily
    >>> and use SAS to process the data. We also have the following in ous
    >>> job.conf:
    >>>
    >>> KEEP_DAYS 10
    >>> KEEP_SUCCESSFUL_DAYS 5
    >>>
    >>> By putting the data to a dataset daily and trimming the job

    >>information as
    >>> we do, the job monitor comes up much more quickly and the jobs data

    >>does not
    >>> get so large.
    >>>
    >>> Kelly
    >>> antilles89 wrote in message
    >>> news:394FEC6A.B70F363@wanadoo.fr...
    >>> > /usr/openv/netbackup/bin/admincmd/bpdbjobs -report -all_columns
    >>> >
    >>> > The result of this is very interessant but i don't know the name of
    >>> > this columns and should i change the columns separate "," to ";" or

    >>TAB
    >>> > or
    >>> > other character.
    >>> >
    >>> > And finally if it possible to get an executing period : one month

    >>for
    >>> > example.
    >>> >
    >>> >

    >>
    >>
    >>

    >
    >
    >Not sure if this is quite what you want, I don't have the need to report
    >on all those thousands of fields. I just use bpdbjobs -report. This has

    no
    >column headings, so [very basic kludge] - i created a text file with the
    >headings manually setup, then run a script to add the bpdbjobs -report on
    >to the end. Somehow i think this is too simple for what you're asking ??.
    >



  4. Re: bpdbjobs !!


    I hope this ill help

    /usr/openv/netbackup/bin/bpdbm -ctime 0950916985


    "Jim Lyons" wrote:
    >
    >Does anyone know how to get the start/elapsed/end times into a readable

    format
    >rather than the epoch format? This is new to 4.5 bpdbjobs as far as I can
    >tell.
    >
    >thanks,
    >Jim
    >
    >
    >"Creaky" wrote:
    >>
    >>antilles89 wrote:
    >>>Kelly, thanks a lot for this information but you know, this JOB:
    >>>
    >>>bpdbjobs -header -report -all_columns
    >>>
    >>>with this i can't see the header and why ?
    >>>
    >>>jobid,jobtype,state,etc...
    >>>
    >>>
    >>>Kelly Wyatt a écrit :
    >>>
    >>>> This is what I got from VERITAS support... I have to figure out what
    >>>some of
    >>>> the fields mean (like jobtype -- a numeric -- what is a backup, a
    >>>> restore...). Below you will see a sample record from my output and
    >>>the
    >>>> fields that I determined went with them.
    >>>>
    >>>> jobid 305
    >>>> jobtype 0
    >>>> state 3
    >>>> status 1
    >>>> class a.unix
    >>>> schedule full
    >>>> client asrv01
    >>>> server aback.unx
    >>>> started 0950916985
    >>>> elapsed 0000011093
    >>>> ended 0950928078
    >>>> stunit a.pc
    >>>> try 1
    >>>> operation ?
    >>>> kbytes 21022930
    >>>> files 416421
    >>>> pathlastwritten ?
    >>>> percent ?
    >>>> jobpid 12944
    >>>> owner root
    >>>> subtype 1
    >>>> classtype 0
    >>>> scheduletype 0
    >>>> priority 0
    >>>> group ?
    >>>> masterserver aback
    >>>> retention units 3
    >>>> retentionperiod 2
    >>>> compression 0
    >>>> kbyteslastwritt 0
    >>>> fileslastwritt 0
    >>>> filelistcount 1
    >>>> files ALL_LOCAL_DRIVES
    >>>> trycount 1
    >>>> trypid 12944
    >>>> trystunit a.pc
    >>>> tryserver aback.unx
    >>>> trystarted 950916985
    >>>> tryelapsed 11093
    >>>> tryended 950928078
    >>>> trystatus 1
    >>>> trystatusdesc the requested operation was partially successful
    >>>> trystatuscount 28
    >>>> trystatuslines 02/18/00 18:36:31 - mounting AU0050
    >>>> 02/18/00 18:36:32 - connecting
    >>>> 02/18/00 18:36:33 - connected; connect time: 000:00:01
    >>>> 02/18/00 19:17:36 - mounted; mount time: 000:41:05
    >>>> 02/18/00 19:17:36 - positioning to file 1
    >>>> 02/18/00 19:18:02 - positioned; position time: 000:00:26
    >>>> 02/18/00 19:18:02 - begin writing
    >>>> 02/18/00 19:32:14 - positioning to file 2
    >>>> 02/18/00 19:32:14 - positioned; position time: 000:00:00
    >>>> 02/18/00 19:41:45 - positioning to file 3
    >>>> 02/18/00 19:41:45 - positioned; position time: 000:00:00
    >>>> 02/18/00 19:52:12 - positioning to file 4
    >>>> 02/18/00 19:52:12 - positioned; position time: 000:00:00
    >>>> 02/18/00 20:01:46 - positioning to file 5
    >>>> 02/18/00 20:01:46 - positioned; position time: 000:00:00
    >>>> 02/18/00 20:10:10 - positioning to file 6
    >>>> 02/18/00 20:10:10 - positioned; position time: 000:00:00
    >>>> 02/18/00 20:18:48 - positioning to file 7
    >>>> 02/18/00 20:18:48 - positioned; position time: 000:00:00
    >>>> 02/18/00 20:32:53 - positioning to file 8
    >>>> 02/18/00 20:32:53 - positioned; position time: 000:00:00
    >>>> 02/18/00 20:47:59 - positioning to file 9
    >>>> 02/18/00 20:47:59 - positioned; position time: 000:00:00
    >>>> 02/18/00 21:03:58 - positioning to file 10
    >>>> 02/18/00 21:03:58 - positioned; position time: 000:00:00
    >>>> 02/18/00 21:23:42 - positioning to file 11
    >>>> 02/18/00 21:23:42 - positioned; position time: 000:00:00
    >>>> 02/18/00 21:41:03 - end writing; write time: 002:23:01
    >>>> trybyteswritten 21022930
    >>>> tryfileswritten 416421
    >>>>
    >>>> I believe you can send a parameter like hoursago or something to get

    >a
    >>>
    >>>> certain time period. Here at SAS, we put the output to a SAS dataset
    >>>daily
    >>>> and use SAS to process the data. We also have the following in ous
    >>>> job.conf:
    >>>>
    >>>> KEEP_DAYS 10
    >>>> KEEP_SUCCESSFUL_DAYS 5
    >>>>
    >>>> By putting the data to a dataset daily and trimming the job
    >>>information as
    >>>> we do, the job monitor comes up much more quickly and the jobs data
    >>>does not
    >>>> get so large.
    >>>>
    >>>> Kelly
    >>>> antilles89 wrote in message
    >>>> news:394FEC6A.B70F363@wanadoo.fr...
    >>>> > /usr/openv/netbackup/bin/admincmd/bpdbjobs -report -all_columns
    >>>> >
    >>>> > The result of this is very interessant but i don't know the name of
    >>>> > this columns and should i change the columns separate "," to ";" or
    >>>TAB
    >>>> > or
    >>>> > other character.
    >>>> >
    >>>> > And finally if it possible to get an executing period : one month
    >>>for
    >>>> > example.
    >>>> >
    >>>> >
    >>>
    >>>
    >>>

    >>
    >>
    >>Not sure if this is quite what you want, I don't have the need to report
    >>on all those thousands of fields. I just use bpdbjobs -report. This has

    >no
    >>column headings, so [very basic kludge] - i created a text file with the
    >>headings manually setup, then run a script to add the bpdbjobs -report

    on
    >>to the end. Somehow i think this is too simple for what you're asking ??.
    >>

    >



+ Reply to Thread