Storix Software SBAdmin User Guide - Manual (Page 140)

It is common to lower this value if you do not want your backups to run as the same priority as other
applications. This will usually cause the backup process to have less affect on the performance of other
applications, but the backup could run a bit slower. You might consider setting this value to 3 to give
backup processes a lower priority, but not so low that the backup takes too much longer.
If you want the backup process to run in the shortest possible time, with no regard to how it might adversely
affect the performance of other applications, you can increase this value. Note that doing so will have little
or no affect if there are no other applications or processes requiring CPU processing, but those that require
the CPU could run slower. In this case, you might consider a setting of 7 to give priority to the backup
without bringing all other applications to a halt.
Setting this option to any value other than 5 will apply to all backup
jobs unless you change the
backup job process priority within the job
profile settings.
Concurrent Backups
For backups to a disk (directory) on a Backup Media Server , multiple backups may be writing to the same
device concurrently. For TSM, SBAdmin has no control over where the backup data is actually stored on
the
TSM server . Therefore, all backups to the TSM server may be run concurrently, even if they are writing
to the same tape library or disk drives.
This may pose a problem on the server for a number of reasons:
1. This may cause degraded I/O performance on the server, affecting other applications.
2. A single large backup to a server’s disk could cause many smaller backups to take much longer since
they must share the same I/O.
3. TSM may simultaneously write multiple backups to the same tape (interspersing the backup data), but
all of the simultaneous backups will be limited by the speed of that single tape drive.
It would make more sense in any case to limit the number of concurrent backups to a manageable number.
To limit the number of disk (or TSM) backups which may be written concurrently to the same server, select
File !Preferences!General Preferences , and enter a number in the Limit concurrent backups to [a disk
or the TSM server] to: field.
By leaving this field blank (or 0), there will be no limit to the number of concurrent backups.
Auto-Terminate Stalled Backups
You may specify the number of minutes to wait before considering a backup as stalled and have the backup
job automatically killed. This preference does not apply to backups written to tape devices because the
timeout could be related to waiting for a new tape when reaching end of media. The default is to wait
forever and not automatically kill the backup job.
A backup is considered to have stalled once all backup pre-processing has completed and backup data
begins to write, but no progress has been made for the length of the defined timeout. If the timeout has
been reached, notification will be sent based on your
notification settings , and a kill signal will be sent to
the backup job.
To define stalled backups timeout select File !Preferences!General Preferences and enter the number of
minutes in the Minutes to wait before killing a stalled backup to a non-tape device field.
Storix System Backup Administrator 140 Version 8.2 User Guide