Job Statuses

The table below describes several statuses for a job.

Status	Description
A	Job canceled by user
B	Job blocked
C	Job created but not yet running
D	Verify differences
E	Job terminated in error
F	Job waiting on File daemon
I	Incomplete Job
L	Committing data (last despool)
M	Job waiting for Mount
R	Job running
S	Job waiting on the Storage daemon
T	Job terminated normally
W	Job terminated normally with warnings
a	SD despooling attributes
c	Waiting for Client resource
d	Waiting for maximum jobs
e	Non-fatal error
f	Fatal error
i	Doing batch insert file records
j	Waiting for job resource
l	Doing data despooling
m	Waiting for new media
p	Waiting for higher priority jobs to finish
q	Queued waiting for device
s	Waiting for storage resource
t	Waiting for start time

I – Incomplete Jobs

An incomplete Job is a Backup Job which has been ended before completion in a situation where the Storage Daemon was able and allowed (per configuration) to commit data to Volumes and to the Catalog that allows the Job to be resumed later on. This usually happens when there is a communication problem between SD and FD, or when the File Daemon fails for some reason.

Note that backups done from dynamically created data sets, for example database dumps or ephemeral file system snapshots, may not be restartable despite the Storage Daemon considering the data to be sufficient for this purpose.

See the console commands restart and stop.