Additional Setup
139
4
Note:
If the backup window closes before NetBackup can start all the jobs in a
multiplexing set, NetBackup completes only the jobs that have actually started.
For example, on the figure above, assume that the NetBackup Activity Monitor
shows A1 through A5 as queued and active. If only A1 and A2 actually start
before the window closes, NetBackup does not perform the other jobs that are
in the set. If the window closes before any jobs have started, then only the first
queued and active job starts and completes (A1 in this example).
Other Configuration Settings to Consider
Maximum Jobs per Class
Set Maximum Jobs per Class high enough to support the specified level of
multiplexing. See “Maximum Jobs per Class” on page 62.
Maximum Jobs per Client
The Maximum Jobs per Client global attribute limits the number of backup
jobs that can run concurrently on any NetBackup client. Usually, its setting
does not affect multiplexing. However, to illustrate its effect, consider a case
where there are jobs from different schedules on the same client and all are
going to the same storage unit. In this case, it is possible for the maximum
number of jobs permitted on the client to be reached before the multiplexing
limit is reached for the storage unit. If this occurs, it prevents NetBackup from
fully utilizing the storage unit’s multiplexing capabilities.
Maximum Jobs this Client
You can also set the maximum number of jobs that are allowed on a specific
client without affecting other clients. For an explanation see “Maximum Data
Streams” on page 486.
MPX Restore Delay
The NetBackup configuration option, Delay On Multiplexed Restores, applies
to multiplexed restores and specifies how long (in seconds) the server waits for
additional restore requests of files and (or) raw partitions that are in a set of
multiplexed images on the same tape.
NetBackup 3.2 System Administrator's Guide for Windows NT
NetBackup 3.2 System Administrator's Guide for Windows NT
