Strunjob – Storix Software SBAdmin Commands Reference User Manual

Page 52

Advertising
background image

Storix System Backup Administrator

- 52 -

Version 8.2 Commands Reference

strunjob

Purpose:

Run a backup job in the foreground

Use on:

Administrator

Syntax:

strunjob JobID

Details:

The strunjob command will perform the backups for all clients configured for the job
(referenced by JobID) just as it would when executed from the job queues. The job status
information, command output and error messages, and backup label information will be saved
for future viewing using the View Backup Labels from the SBAdmin GUI or Web Interface. The
command output and error messages will also be sent to standard output and standard error,
shown on the screen by default. If you wish to save this output to a file, you may type the
command as follows:

strunjob JobID > filename 2>&1

The strunjob command will continue running until all clients in the job have been backed up or
until an error causes the command to terminate. The command will exit with one of the
following return codes, indicating the status of the job:

0

Job completed successfully

1

Job terminated because a client backup failed. Since partial data has been written to the
media, no additional client backups have been started. Failure of a client backup may
be due to a media write error or a network failure.

2

Job terminated due to an error that occurred while saving the backup command output,
status information, or label information.

3

Job terminated due to an error in pre-processing tasks. This might include such things
as a backup device already in use or the backup server or network unavailable.

4

The client backups completed, but a post-processing error occurred. This might include
the inability to update the backup label or history information after the backup
completes, or an error ejecting the tape from the drive when the job requires the tape to
be ejected when complete.

5

Client backups completed but a minor error occurred in post-processing. Should not
affect the backup history or label, nor should it affect other jobs appended to the same
media.

6

The job completed successfully, but one or more clients in the job were not included in
the backup. The reason may be because the client or network was unavailable or
because the client could not reach the server over the network. This error will also occur

Advertising