Storix Software SBAdmin Commands Reference User Manual
Page 43
Storix System Backup Administrator
- 43 -
Version 8.2 Commands Reference
Adding a Job to the Queue
Use the –A option to add a pre-defined backup job to the queue. If there are jobs in the same
queue, the added job will be run after all prior jobs in the same queue complete. Note, if a prior
job had failed, the queue will not process any new jobs until the failed job is either restarted or
removed. Refer to the Job Queues section of the
SBAdmin User Guide
for information on
monitoring/changing the status of queues using the SBAdmin GUI or Web Interface.
When jobs are run from the queue and the SBAdmin GUI or Web Interface is not running, no
job status messages will be reported on the screen. Status messages, in this case, will always
be reported using the Alternate Notification method (mailed to a user or appended to a text
file). The backup output and progress information may later be displayed after running the
SBAdmin GUI or Web Interface and selecting the
options.
Note that the stqueue command will return as soon as the job is added to the queue. The exit
code of this command will be 0 if the job was queued successfully, or 1 if the job could not be
queued (usually because the JobID supplied is invalid). If, for instance, the server for the job is
not available, the stqueue command will succeed, but the job will fail after it is executed by
the queuing system, and will remain in the queue until it is restarted or removed.
Killing a Running Job
To kill a job that is currently running, use the –K flag. This will sent a kill signal to the backup
process. It may take some time for the job to stop since it may be necessary to complete the
current operation before the process will die.
When a job configured to write to tape is killed, it will remain in the queue in a “failed” state,
which will prevent other jobs in the same queue from starting. Jobs that write to disk image
files will be automatically removed from the queue, since “disk” queues will allow jobs to run
simultaneously anyway.
When a job is killed, the tape drive, if used, will be rewound to prevent any other backup jobs
from being appended to an incomplete backup. If the Tape Overwrite/Retention Policy does
not allow overwriting of current (unexpired) backups, any subsequent jobs started after
removing the failed job from the queue will fail with an overwrite protection error. If this is the
case, use the
program to expire the failed backup label. Then restart the queue
to allow other jobs to continue.
Removing a Job from the Queue
Use the –D flag to delete a job from the queue. Removing a job from the queue will not delete
the original job information, but only removes it from the queue. It can be resubmitted using
the –A option if desired. You cannot delete a job from the queue if it is currently running. To
delete a job already running, first kill it with the –K option.
Displaying Job Output
If a job has failed, it may be necessary to display the output messages of the backup
command to determine the cause. To do so, specify the –S option. The progress indicator
(indicating the percentage of backup data written to the media), output and error messages of
the backup command will be displayed to standard output.
If this option produces no output, then the backup command had not yet started. If the job had
failed, it is due to a pre-backup error such as a tape overwrite protection error, or because a
device or server was unavailable. In these cases, the message indicating the problem was
sent using the notification process defined in the preferences options.