The following items appear in the job details tabs:
Active Start |
The time when the most recent attempt became active. |
Active Elapsed |
The time since the most recent attempt became active. |
Attempt |
For Active jobs, the number of the current attempt. For Done jobs, the total number of attempts. |
cache hits |
For deduplication jobs, the percentage of time that the local fingerprint cache contained a record of the segment. The deduplication plug-in did not have to query the database about the segment. |
Client |
The name of the client that is associated with the job. |
Copy |
The copy number when the multiple copies are created. |
Current File |
For Active jobs, the path of a file that was recently written to the image. If the job backs up many files, not all of them necessarily appear in this column over the course of the backup. |
Current Files Written |
The number of files that have been written so far. |
Current Kilobytes Written |
The number of kilobytes that have been written so far. For deduplication jobs, the amount that is written may be larger than the data size on the client. The amount that is written includes additional data such as tar headers and NetBackup catalog information. |
CR sent |
For deduplication jobs, the amount of data that is sent from the deduplication plug-in to the component that stores the data. (In NetBackup, the NetBackup Deduplication Engine stores the data. In PureDisk, a content router stores the data.) If the storage server deduplicates the data, it does not travel over the network. The deduplicated data travels over the network when the deduplication plug-in runs on a computer other than the storage server, as follows:
|
Data Movement |
Distinguishes between the various types of jobs: Standard (results from a regular backup), Synthetic (backup), or Disk Staging. If the Snapshot Client is licensed, additional entries can include: Instant Recovery Disk, Instant Recovery Disk and Tape, and Snapshot. |
Data on PDDE Storage |
For deduplication jobs, the amount of data that is stored for the job. |
dedup |
For deduplication, the percentage of data that was stored already. That data is not stored again. |
Deduplication Rate |
For deduplication jobs, the percentage of data that was stored already. That data is not stored again. |
Elapsed Time |
The amount of time that has elapsed since the job was initially queued. |
End Time |
The date and time that the operation completed. |
Estimated Files |
An estimate of the number of files to be written for the job. |
Estimated Kilobytes |
An estimate of the number of kilobytes to be written for the job. |
Files |
The number of files that have been written. |
Job ID |
The identifier that NetBackup assigns to each job. The identifier is unique on the server where the job was run. |
Job PID |
The ID of the current job process. Parent and children jobs have the same PID. |
Job State |
Note that nbemm must be running in order for jobs to run.The following are job states:
|
KB Per Second |
The average data transfer rate in kilobytes per second over the length of the current attempt. |
Kilobytes |
The number of kilobytes that were written. For deduplication jobs, the amount that is written may be larger than the data size on the client. The amount that is written includes additional data such as tar headers and NetBackup catalog information. |
Master Server |
The master server on which the job is run. |
Media Server |
The NetBackup server controlling the media. |
Media to Eject |
The number of tapes to be ejected for the selected Vault job. The number may not represent the number of tapes that have ejected. For example, if the Vault profile was configured for manual eject, the tapes may not have yet been ejected. Or, if something went wrong with the device, fewer tapes may have been ejected than the number here indicates. |
Off-host Type |
Indicates the off-loading of backup processing to a separate backup agent that runs on another host. Additionally licensed products such as Snapshot Client are required for these off-host backups types as follows:
|
Operation |
For Active jobs, indicates the operation currently performed. |
Owner |
The owner of the job. |
Parent JobID |
Indicates the parent job ID of a composite job. Vault, for example, is a composite job that consists of a single parent, followed by multiple child jobs. The Parent Job ID number is followed in sequence by the child job ID numbers. Each job is represented in an individual line in the Jobs tab. |
% Complete (Estimated) |
The percentage of the job that is complete. For backups, it is based on the size of the previous backup for the same policy, client, schedule, and retention period. If there is no previous backup that matches this criteria, NetBackup does not provide an estimate. If the current backup is larger, this indication is 100%. For other types of jobs, the estimate is based on other factors. |
Policy |
The name of the policy that NetBackup uses to back up the client. If the policy is associated with a disk staging storage unit, the name follows the convention: __DSSU_POLICY_storageunitname |
Profile |
The profile defines Vault job tasks. Multiple profiles can be configured for the Vault. |
Robot |
For a Vault job, the name of the robot with which Vault is associated. |
scanned |
For deduplication jobs, the amount of data that the deduplication plug-in scanned. |
Schedule |
The name of the schedule that NetBackup uses to back up the client. |
Session ID |
The session ID for a Vault session. The session ID is a unique numeric value. Session ID assignment starts at 1 the first time a Vault session is run after Vault is installed. The value increments by one every time a new Vault session runs. |
Start Time |
The date and time that the first attempt was initially queued. |
State Details |
The reason why a job is queued. There may be a delay between when the job appears as Queued and when the queue reason is displayed. When a job is initiated, it enters a queue to be awarded a resource. An analogous situation is the check-in line at the airport: the traveler may wait a while to reach the front of the line and be given a boarding pass. Similarly, a job enters a queue behind other jobs that wait to be assigned to media servers, robots, drives, and media. When the job reaches the front of the queue, the necessary resources may be busy. At that point, the job is not in a queue for resource selection, but in a queue for specific resources. When the specific resources are identified, the State Details column can convey the information. |
Status |
The status code and the text that describes the completion status of each job attempt. A status of zero (0) means that the job completed successfully. Any other completion value for status indicates a problem. REQUESTING_RESOURCE appears when a job makes an initial request for resources. Examples of the jobs that require resources include the following: backup jobs, restore jobs, media jobs, and the jobs that result from using tpreq, bplabel, tpclean, and vmphyinv. GRANTED_RESOURCE appears as resources are allocated. AWAITING_RESOURCE appears if the job is queued due to unavailability of resources. Parent job details display the following entries for each operation that the parent job executes: the operation step being executed the status of the operation once it completes the time the operation ended For example, the Detailed Status tab contains Parent Job as the first operation performed. The status that is associated with the parent job operation indicates the final job status that is returned to the Job Manager (nbjm): BEGIN_OPERATION Parent Job STATUS 0 END_OPERATION 1230065211 |
Storage Unit |
The name of the storage unit that the job uses. |
stream rate |
For deduplication, the speed of the scan: The kilobytes of data that are scanned divided by how long the scan takes. |
Transport |
Applies when the SAN Client license is installed. The type of transport between the SAN client and the NetBackup media server: FT (fibre-accelerated transport), LAN (local area network), or SHM (shared memory). |
Type |
See Type column. |
Vault |
The name of the logical Vault for a robot that is configured through the Vault Management node. (Appears for Vault jobs only.) |
More Information