Global attributes properties
To access this setting, in the web UI select . Select the primary server. If necessary click , then click . Click .
The Global attributes properties apply to currently selected primary servers. These properties affect all operations for all policies and clients. The default values are adequate for most installations.
The Global attributes page contains the following properties.
Table: Global attributes properties
Property | Description |
|---|---|
This property specifies how often NetBackup retries a job. The default is 10 minutes. The maximum is 60 minutes; the minimum is 1 minute. | |
This property specifies the throttle on the maximum number of backup jobs that are allowed to go from the Queued to Active state per second. By default, the value of this property is 0, which means no throttling occurs. After the maximum number of jobs is reached in one second, subsequent jobs will remain in the Queued state. In the next second, jobs are released in a first-in-first-out order from the Queued state until the maximum jobs value is reached again or until all throttled jobs or new jobs have been made active. This property can be used to smooth out the resource utilization curve. It is particularly useful when backup windows open and a large number of jobs are scheduled to start within a short time period. This value supersedes the DBM_NEW_IMAGE_DELAY configuration value found here: https://www.veritas.com/support/en_US/article.100047119 If DBM_NEW_IMAGE_DELAY is configured and the maximum jobs per second throttle is the default value, the DBM_NEW_IMAGE_DELAY will be converted to an equivalent jobs-per-second value. It will not modify the configuration. For example, if DBM_NEW_IMAGE_DELAY was set to 333ms, the NetBackup Job Manager will use a maximum jobs per second throttle of 3. If the user then configured the maximum jobs throttle to 2 per second, the configured DBM_NEW_IMAGE_DELAY would be ignored. Note: This throttle only affects the number of backup jobs that the NetBackup Job Manager allows to start in one second. It does not affect other job types like restores, archives, duplications, or replications. It does not affect the maximum number of concurrent jobs. | |
This property specifies the maximum number of backup and archive jobs that NetBackup clients can perform concurrently. The default is one job. NetBackup can process concurrent backup jobs from different policies on the same client only in the following situations:
| |
This property specifies how long NetBackup waits to process a policy after a policy is changed. The interval allows the NetBackup administrator time to make multiple changes to the policy. The default is 10 minutes. The maximum is 1440 minutes; the minimum is 1 minute. | |
This property specifies how long NetBackup waits after a backup before it compresses the image catalog file. | |
NetBackup considers the failure history of a policy to determine whether or not to run a scheduled backup job. The property sets the timeframe for NetBackup to examine. This property determines the following characteristics for each policy:
Consider the following example scenario using the default setting 2 tries every 12 hours:
Note: This attribute does not apply to user backups and archives. | |
This property specifies the maximum number of vault jobs that are allowed to be active on the primary server. The greater the maximum number of vault jobs, the more system resources are used. If the active vault jobs limit is reached, subsequent vault jobs are queued and their status is shown as Queued in the Activity monitor. If a duplication job or eject job waits, its status is shown as Active in the Activity monitor. | |
This property specifies the addresses where NetBackup sends notifications of scheduled backups or administrator-directed manual backups. To send the information to more than one administrator, separate multiple email addresses by using a comma, as follows: useraccount1@company.com,useraccount2@company.com More information is available on the configuration requirements for email notifications. See Send notifications to the backup administrator about failed backups. |