Storix Software SBAdmin User Guide - Manual (Page 80)

Storix System Backup Administrator 80 Version 8.2 User Guide
Running a Backup Job on Demand
Any backup job, whether it is currently scheduled or not, may be run at any time. There are several ways to
start a job running:
1. Select Configure !Backup Jobs or Actions !Run a Backup Job from the menu bar, then select the Job
ID at the top of the screen and press the Run Now button.
2. If the Job Information is displayed on the Main Screen , select the icon for the job to run and press the
Run button at the bottom of the screen.
3. If the job is currently at the top of a job queue but is not running because it had previously failed or was
placed on hold, display the job queues on the Main Screen , select the queue in which the job is placed,
and then press the Restart button.
For the first two options, "running" the job actually just places the job in the job queue . If there are no other jobs
in the same queue, the job will start running immediately. When a job is added to the queue, it will be run
immediately if there are no other jobs queued to the same device on the same server (except that disk file
backups on a server may run simultaneously). If another job is running to the same device, this job will be
placed in a “Pending” state until the prior job finishes. If a prior job had failed, it will remain in the queue and
block other jobs from starting. The failed job must therefore be either restarted or removed from the queue to
allow jobs behind it to start.
Adding a Job to the Queue from the Command Line
Even if the Backup Administrator user interface is not running, scheduled jobs will automatically be placed
in the queue at their scheduled times, and the queues will be processed and jobs in each queue will be run
on a first-come first-serve basis. It is also possible to manually add jobs to the queue without using the
SBAdmin interface. To add a job to the queue, refer to the stqueue command in the
Commands
Reference Guide .
Running a Backup Job from the Command Line
It is possible to run a backup job from the command line, bypassing the job queues, by using the strunjob
command (refer to the strunjob command in the
Commands Reference Guide ). The Backup
Administrator user interface need not be running. Note that the job will start immediately and may interfere
with other jobs writing to the same devices since the queues are not used. If you wish to add the job to the
queue from the command line, so that it will run only when the backup server and devices are available,
refer to the section
Adding a Job to the Queue from the Command Line .
Automatically Copying Backups
This option is not available for TSM Edition, but may be used to copy to a TSM server
when the optional TSM Backup Feature is installed. This option may only be used if
the original backup is written to a directory device.
You may configure a backup job so that each time it completes, the new backup is automatically copied to
another backup server or device. This is often referred to as a Second-Stage Backup, or (depending on the
destination media) D2D2T (disk-to-disk-to-tape) or D2D2D (disk-to-disk-to-disk). Use this option if, for instance,
a backup job is configured to backup one or more clients to a directory on a local network server, and you want
to later copy those backups to another server or device (including tape, directory, NFS or TSM server).
This option allows the copying to take place automatically each time the job completes without any user
intervention. You may still continue to manually copy backups from one server or media to another using the