About constraints on the number of concurrent jobs
Specify any number of concurrent jobs within the following constraints.
Table: Constraints on concurrent jobs
Constraint | Description |
|---|---|
Number of storage devices | NetBackup can perform concurrent backups to separate storage units or to drives within a storage unit. For example, a single Media Manager storage unit supports as many concurrent backups as it has drives. A disk storage unit is a directory on disk, so the maximum number of jobs depends on system capabilities. |
Server and client speed | Too many concurrent backups on an individual client interfere with the performance of the client. The best setting depends on the hardware, operating system, and applications that are running. The property applies to all clients in all policies. To accommodate weaker clients (ones that can handle only a small number of jobs concurrently), consider using one of the following approaches:
|
Network loading | The available bandwidth of the network affects how many backups can occur concurrently. The load might be too much for a single Ethernet. For loading problems, consider backups over multiple networks or compression. A special case exists to back up a client that is also a server. Network loading is not a factor because the network is not used. Client and server loading, however, is still a factor. |
Note:
Catalog backups can run concurrently with other backups.
To do so, set Maximum jobs per client to a value greater than Maximum number of streams that is configured for the catalog policy for the primary server. For example, if Maximum number of streams is set to 4, Maximum jobs per client should be set to 5 or to a greater value.