<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Veeam Backup Job Status Advanced Sensor

The Veeam Backup Job Status Advanced sensor monitors the status of a specific backup job that runs on the Veeam Backup Enterprise Manager.

Veeam Backup Job Status Advanced Sensor

Veeam Backup Job Status Advanced Sensor

i_square_cyanFor a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Sensor in Other Languages

  • Dutch: Veeam Backup Job Status Advanced
  • French: Veeam État de tâche de sauvegarde avancée
  • German: Veeam Backupjob-Status (Erweitert)
  • Japanese: Veeam バックアップジョブステータス詳細
  • Portuguese: Status da tarefa de backup do Veeam (Avançado)
  • Russian: Расширенное состояние задания резервного копирования Veeam
  • Simplified Chinese: Veeam 备份作业状态高级
  • Spanish: Estado del trabajo de Veeam Backup (avanzado)

Remarks

  • This sensor requires that the Veeam Backup Enterprise Manager 10 or 11 with the Enterprise Plus license are installed.
  • This sensor does not support the following backup job types: Tape, Sure Backup, NAS Backup Copy, and Agent Backup Copy.
  • This sensor does not support Veeam Agent Backup Jobs if they are managed by a Veeam Agent.
  • This sensor only supports version 1.5 of the Representational State Transfer (REST) application programming interface (API).
  • This sensor supports IPv6.
  • This sensor has a very low performance impact.
  • This sensor uses lookups to determine the status values of one or more channels.

Basic Sensor Settings

Basic Sensor Settings

Basic Sensor Settings

Setting

Description

Sensor Name

Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.

i_round_blueIf the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?

Parent Tags

The tags that the sensor inherits from its parent device, parent group, and parent probe.

i_round_blueThis setting is for your information only. You cannot change it.

Tags

Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.

i_round_blueIt is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

i_round_blueFor performance reasons, it can take some minutes until you can filter for new tags that you added.

The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:

  • veeam
  • veeambackup
  • veeamenterprisemanager

Priority

Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority (i_priority_1) to the highest priority (i_priority_5).

Veeam Specific

Veeam Specific

Veeam Specific

Setting

Description

Job Name

The name of the backup job that this sensor monitors.

Job Type

The type of backup job that this sensor monitors.

Platform

The platform on which the backup job runs.

Job Description

The description of the backup job that this sensor monitors.

Sensor Display

Sensor Display

Sensor Display

Setting

Description

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.

i_round_blueYou can set a different primary channel later by clicking b_channel_primary below a channel gauge on the sensor's Overview tab.

Graph Type

Define how different channels are shown for this sensor:

  • Show channels independently (default): Show a graph for each channel.
  • Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
    i_round_redYou cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This setting is only visible if you select Stack channels on top of each other above.

Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

Debug Options

Debug Options

Debug Options

Setting

Description

Result Handling

Define what PRTG does with the sensor result:

  • Discard result: Do not store the sensor result.
  • Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file name is Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites this file with each scanning interval.

i_podThis option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.

i_round_blueIn a cluster, PRTG stores the result in the PRTG data directory of the master node.

Inherited Settings

By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click b_inherited_enabled under the corresponding setting name to disable the inheritance and to display its options.

i_square_cyanFor more information, see section Inheritance of Settings.

Scanning Interval

i_round_blueThe minimum scanning interval of this sensor is 1 minute.

i_round_blueThe recommended scanning interval of this sensor is 5 minutes.

Scanning Interval

Scanning Interval

i_square_cyanFor more information, see section Root Group Settings, section Scanning Interval.

Schedules, Dependencies, and Maintenance Window

i_round_blueYou cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.

Schedules, Dependencies, and Maintenance Window

Schedules, Dependencies, and Maintenance Window

i_square_cyanFor more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.

Access Rights

Access Rights

Access Rights

i_square_cyanFor more information, see section Root Group Settings, section Access Rights.

Channel Unit Configuration

i_round_blueWhich channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.

Channel Unit Configuration

Channel Unit Configuration

i_square_cyanFor more information, see section Root Group Settings, section Channel Unit Configuration.

Channel List

i_round_blueWhich channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.

Channel

Description

Downtime

In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status

Duration

The duration of the backup job run

Job Scheduled

If the backup job is scheduled

Last Job Run

The time since the last backup job run

Last Result

The last backup job run status

  • Up status: Successful
  • Warning status: Warning
  • Down status: Failed
  • Unknown status: None

i_round_blueThis channel is the primary channel by default.

Status

The backup job run status

  • Up status: Starting, Working, Stopped
  • Warning status: Stopping, Pausing, Resuming, Never started, Postprocessing
  • Unknown status: Idle

More

i_square_blueKNOWLEDGE BASE

How can I change the status of my Veeam sensors based on whether a job is scheduled or not?