Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Administrator's Guide, Volume I
  3. Section II. Configuring hosts
  4. Configuring Host Properties
  5. Global Attributes properties
  6. About constraints on the number of concurrent jobs
Veritas NetBackup™ Administrator's Guide, Volume I

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 Maximum jobs per client 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:

  • Set the Maximum data streams property for those weaker client(s) appropriately. (This property is found under Host Properties > Master Servers > Double-click on a specific master server > Client Attributes > General tab.)

    See General tab of the Client Attributes properties.

  • Use the Limit jobs per policy policy setting in a client-specific policy. (A client-specific policy is one in which all clients share this characteristic).

Network loading

The available bandwidth of the network affects how many backups can occur concurrently. Two Exabyte 8500, 8mm tape drives can create up to a 900-kilobyte-per-second network load. Depending on other factors, 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.

Figure: Maximum jobs per client

Maximum jobs per client

Note:

Catalog backups can run concurrently with other backups. To do so, set the Maximum jobs per client value to greater than two for the master server. The higher setting ensures that the catalog backup can proceed while the regular backup activity occurs.

More Information

Limit jobs per policy (policy attribute)

Feedback

Was this page helpful?
Previous

Global Attributes properties

Next

Setting up mailx email client

Feedback

Was this page helpful?