Veritas NetBackup™ Commands Reference Guide

Displays all columns of a report or summary. The following are descriptions of the fields:

field1 = Job ID

field2 = Job type

0=backup, 1=archive, 2=restore, 3=verify, 4=duplicate, 5=phase 1 or phase 2 import, 6=catalog backup, 7=vault duplicate, 8=label tape, 9=erase tape, 10=tape request, 11=clean tape, 12=format tape, 13=physical inventory of robotic library, 14=qualification test of drive or robotic library, 15=catalog recovery, 16=media contents, 17=image cleanup, 18=LiveUpdate, 20=Replication (Auto Image Replication), 21=Import (Auto Image Replication), 22=backup From Snapshot, 23=Replication (snap), 24=Import (snap), 25=application state capture, 26=indexing, 27=index cleanup, 28=Snapshot, 29=SnapIndex, 30=ActivateInstantRecovery, 31=DeactivateInstantRecovery, 32=ReactivateInstantRecovery, 33=StopInstantRecovery, 34=InstantRecovery

field3 = State of the job

0=queued and awaiting resources, 1=active, 2=requeued and awaiting resources, 3=done, 4=suspended, 5=incomplete

field4 = Job status code

field5 = Policy name for the job

field6 = Job schedule name

field7 = Client name

field8 = Media server used by the job

field9 = Job started time

field10 = Elapsed time for the job

field11 = Job end time

field12 = Storage unit used by the job

field13 = Number of tries

field14 = Operation

0=tape mount, 1=tape positioning, 2=NetBackup connecting to a media server, 3=write to tape, 4=choose images, 5=duplicate image, 6=choose media, 7=catalog backup, 8=tape eject and report, 10=read from tape, 11=duplicate, 12=import, 13=verify, 14=restore, 15=catalog-backup, 16=vault operation, 17=label tape, 18=erase tape, 19=query database, 20=process extents, 21=organize readers, 22=create snapshot, 23=delete snapshot, 24=recover DB, 25=media contents, 26=request job resources, 27=parent job, 28 =indexing, 29=duplicate to remote master, 30=running

field15 = Amount of data written in kilobytes

field16 = Number of files written

field17 = Last written path

field18 = Percent complete

field19 = Job PID

field20 = User account (owner) that initiates the job

field21 = Subtype

0=immediate backup, 1=scheduled backup, 2=user-initiated backup or archive, 3=quick erase of tape, 4=long erase of tape, 5=database backup staging

field22 = Policy type

0 = Standard (UNIX and Linux clients), 4 = Oracle, 6 = Informix-On-BAR, 7 = Sybase, 8 = MS-SharePoint portal server, 11 = DataTools-SQL-BackTrack, 13 = MS- Windows, 15 = MS-SQL-Server, 16 = MS-Exchange-Server, 17 = SAP, 18 = DB2, 19 = NDMP, 20 = FlashBackup, 25 = Lotus Notes, 29 = FlashBackup-Windows, 35 = NBU-Catalog, 39 = Enterprise_Vault, 40 = VMware, 41 = Hyper-V

field23 = Schedule type

0=full, 1=incremental, 2=user backup, 3=user archive, 4=cumulative-incremental, 5=tlog (transaction log backup)

field24 = Job priority assigned to this job as configured in the policy attributes

field25 = Server group name

field26 = Master server name

field27 = Retention level

field28 = Retention period

field29 = Compression

0=disabled, 1=enabled

field30 = Estimated number of kilobytes to be written

field31 = Estimated files to be written

field32 = File list count. The number of files written.

field33 = Comma delimited list of file paths written

field34 = Try count. The number of tries for the job ID

field35 = Try information. A comma-delimited list of try status information

trypid=try PID, trystunit=storage unit, tryserver=server, trystarted=time in epoch the try began, tryelapsed=elapsed time, tryended=time in epoch the try ended, trystatus=try status code, trystatusdescription, trystatuscount=number of comma delimited strings in trystatuslines below, trystatuslines=try status output, trybyteswritten=amount of data written in kilobytes, tryfileswritten=number of files written

field36 = Parent job number

field37= kbpersec - Data transfer speed in kilobytes/second

field38 = Copy number

field39 = Robot - Robotic library used for the job

field40 = Vault ID

field41 = Vault profile

field42 = Vault session

field43 = Number of tapes to eject

field44 = Source storage unit

field45 = Source media server

field46 = Source media ID

field47 = Destination media ID

field48 = Stream number

field49 = Suspendable operation: 0=not suspendable, 1=suspendable

field50 = Resumable operation: 0=not resumable, 1=resumable

field51 = Restartable: 0=not restartable, 1=restartable

field52 = Data movement type

0=standard, 1=IR disk only, 2=IR disk and storage unit, 3=synthetic, 4=disk staging, 5=snapshot

field53 = Snapshot operation: 0=not using snapshot, 1=using snapshot

field54 = Backup ID

field55 = Killable operation: 0=not killable, 1=killable

field56 = Controlling host. Host running the active PID for this job.

field57 = Off-host type

field58 = Fiber Transport usage. 0=lan, 1=ft

field59 = Queue reason

0=unknown reason, 1=media is in use, 2=drives are in use, 3=Tape media server is not active, 4=robotic library is down on server, 5=max job count reached for storage unit, 6=waiting for media request delay to expire, 7=local drives are down, 8=media is in a drive that NetBackup is using, 9=physical drives not available for use, 10=cleaning media not available for use, 11=drive scan host not active, 12=disk media server is not active, 13=media server is currently not connected to master server, 14=media server is not active node of cluster, 15=storage unit concurrent jobs throttled, 16=job history indicates that drives are in use, 17=disk volume temporarily unavailable, 18=max number of concurrent disk volume readers reached, 19=disk pool unavailable, 20=ft pipes in use, 21=disk volume unmounting, 22=disk volume in use, 23=max partially full volumes reached, 24=limit reached for logical resource, 25=drives in use in storage unit, 26=waiting for shared tape drive scan to stop, 27=waiting for mount of disk volume, 28=mountpoint for tape already exists, 29=pending action, 30=max I/O stream count reached for disk volume

field60 = Optional reason string in the following format: reason string (resource queued on)

field61 = Deduplication ratio percent

field62 = Accelerator optimization

field63 = Instance database name

The output of this command consists of a single line per backup job. Each line of the output is a comma-delimited list in the following format:

jobid,jobtype,state,status,policy,schedule,client
server,started,elapsed,ended,stunit,tries,operation,kbytes,
files,pathlastwritten,percent,jobpid,owner,subtype,policytype,
scheduletype,priority,group,masterserver,retentionlevel
,retentionperiod,compression,kbytestobewritten,filestobe
written,filelistcount,[files],trycount,[trypid,trystunit,
tryserver,trystarted,tryelapsed,tryended,trystatus,trys
tatusdescription,trystatuscount,trystatuslines,trybytes
written,tryfileswritten],parentjob,kbpersec,copy,robot,
vault,profile,session,ejecttapes,srcstunit,srcserver,src
media,dstmedia,stream,suspendable,resumable,restartable,
datamovement,snapshot,backupid,killable,controllinghost,
offhosttype,ftusage,queuereason,reasonstring,dedupratio,
acceleratorOptimization,instancedbname

Appends the output to the file that the -file option specifies. If no -file option is provided, the output goes to stdout.

Causes bpdbjobs to cancel active jobs cleanly that appear with a status code of 150 in the Activity Monitor. For example:

bpdbjobs -cancel 11328
bpdbjobs -cancel 11328,11329,11330

Possible jobtype values are listed in the Description section.

Causes bpdbjobs to cleanly cancel all incomplete jobs that appear with a Status 150 in the Activity Monitor. For example:

bpdbjobs -cancel_all

Changes the priority of the specified job or jobs.

Causes bpdbjobs to delete the completed jobs that are older than a specified time period. Use with the -keep_hours or -keep_days, or -keep_successful_hours or -keep_successful_days parameters to specify a retention period. For example:

bpdbjobs -clean -keep_hours 30

Deletes the completed jobs that appear in the Activity Monitor. Multiple job IDs can be deleted in one command. For example:

bpdbjobs -delete 11328,11329,11330

Possible jobtype values are listed in the Description section.

Retrieves the job metadata from bpjobd, but the try file and files file is read directly from the file system. This option is ignored if bpdbjobs is started from a remote host (a host that is not the master).

Names a file to which the output of bpdbjobs is written. If no -file option is provided, the output goes to stdout.

Displays less of the information in a report than -most_columns.

Ignores the parent jobs for the -report and -summary options.

Reports on multiple job IDs.

Possible jobtype values are listed in the Description section.

Used with the -clean option to specify how many days bpdbjobs keeps completed jobs. Default is three (3) days.

Used with the -clean option to specify how many hours bpdbjobs keeps completed jobs. Default is 72 hours.

Used with the -clean option to specify how many days bpdbjobs keeps successful completed jobs. Default is three (3) days.

This value must be less than the -keep_days value.

Used with the -clean option to specify how many hours bpdbjobs keeps successful completed jobs. Default is 72 hours.

This value must be less than the -keep_hours value.

Reports in long format.

Displays the additional columns specific to Vault jobs.

Applies to an environment with multiple master servers. Use the -M option to summarize jobs, delete jobid(s), cancel jobid(s), and cancel all active job IDs for a specific master server:

By default, bpdbjobs translates the start or the end times to be relative to the local clock. A job that starts 10 minutes ago looks like it starts 10 minutes ago regardless of time zone and clock differences with the master server. This option, however, circumvents that translation so that time values are consistent between admin clients.

Behaves similarly to -all_columns but does not print the file list or any information on previous attempts. The -most_columns option is significantly faster than -all_columns.

Prevents the header from being printed in the report.

Cancels the reporting of the number of jobs resumed, suspended,deleted, and canceled.

Indicates the reason why you are performing this command action. The reason text string that you enter is captured and appears in the audit report. The string must be enclosed by double quotes ("...") and cannot exceed 512 characters. It cannot begin with a dash character (-) nor contain a single quotation mark (').

Provides a report of data that is stored in the Activity Monitor. If no option is specified with bpdbjobs, -report is the default option.

Cleanly restarts a job that jobtype indicates. This option supports backups and enables you to restart a job by typing the word BACkup in the Activity Monitor.

Resumes the jobs that job1,job2,...jobn specify, all eligible checkpoint backups or restore the jobs that jobtype indicates, or all eligible jobs if type=all is specified.

Possible jobtype values are listed in the Description section.

Sets the priority of the specified job or jobs to the specified priority number.

Prints a summary line to stdout for all the jobs that are stored in NBU/jobs. Parameters -U and -L format the output of the command. Use the -file option to write the output to a given directory or file name. For example:

bpdbjobs -summary -U -file /tmp/summary.out

Suspends the jobs that job1,job2,...jobn specifies or all eligible checkpoint backups or restore the jobs that jobtype indicates, or all eligible jobs if type=all is specified.

Possible jobtype values are listed in the Description section.

Fetches the job records which have completed after the specified timestamp. The timestamp is specified in the following format:

mm/dd/yyyy hh:mm:ss

The required date and time values format in NetBackup commands varies according to your locale. The /usr/openv/msg/.conf file (UNIX) and the install_path\VERITAS\msg\LC.CONF file (Windows) contain information such as the date-time formats for each supported locale. The files contain specific instructions on how to add or modify the list of supported locales and formats.

For more information about the locale of your system, see "About specifying the locale of the NetBackup installation" in the NetBackup Administrator's Guide, Volume II.

Reports in user format. NetBackup report-generating tools such as the NetBackup-Java Reports application uses this report format.

Displays the additional columns specific to Vault jobs.

Causes bpdbjobs to log additional information in the debug log in the following directory, if the directory exists:

On UNIX systems:

/usr/openv/netbackup/logs/bpdbjobs/*

On Windows systems:

install_path\NetBackup\logs\bpdbjobs\*

Prints the version string, then halts. Any other switches are ignored.