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. NetBackup™ Web UI Administrator's Guide
  3. Section III. Configuring hosts
  4. Managing host properties
  5. Default job priorities properties
NetBackup™ Web UI Administrator's Guide

Default job priorities properties

To access these settings, in the web UI select Hosts > Host properties. Select the primary server and click Edit primary server. Then click Default job priorities.

The Default job priorities host properties let administrators configure the default job priority for different job types.

The job priority can be set for individual jobs in the following utilities:

  • In the Jobs tab of the Activity monitor for queued or active jobs.

  • In the Catalog utility for verify, duplicate, and import jobs.

  • In the Backup, Archive, and Restore client interface for restore jobs.

The Default job priorities page contains the following properties.

Table: Default job priorities properties

Property

Description

Job type

The type of job.

Job priority

The priority that a job has as it competes with other jobs for backup resources. The value can range from 0 to 99999. The higher the number, the greater the priority of the job.

A new priority setting affects all the policies that are created after the host property has been changed.

A higher priority does not guarantee that a job receives resources before a job with a lower priority. NetBackup evaluates jobs with a higher priority before those with a lower priority.

However, the following factors can cause a job with a lower priority to run before a job with a higher priority:

  • To maximize drive use, a low priority job may run first if it can use a drive that is currently loaded. A job with a higher priority that requires that the drive be unloaded would wait.

  • If a low priority job can join a multiplexed group, it may run first. The job with a higher priority may wait if it is not able to join the multiplexed group.

  • If the NetBackup Resource Broker (nbrb) receives a job request during an evaluation cycle, it does not consider the job until the next cycle, regardless of the job priority.

Feedback

Was this page helpful?
Previous

Add a data classification

Next

Understanding the job priority setting

Feedback

Was this page helpful?