Skip to main content
Backup

NovaStor backup

Use the NovaStor backup check to evaluate a device's backup jobs on the server from the data synchronized from NovaStor DataCenter.

The NovaStor backup check evaluates a device's backup jobs from the data octoja synchronizes from NovaStor DataCenter. The check runs on the server every 30 minutes by default and does not depend on the device's operating system. It runs nothing on the device, and octoja does not start, change, or delete backup jobs.

Prerequisites

  • The NovaStor DataCenter integration is connected. Open Administration → Integrations, and under Other platforms click Set up for NovaStor DataCenter, and enter the Data center URL, Username, and Password. Test credentials verifies them, and Save connects the integration. This requires the Integration Management permission.
  • Using Match customers, a NovaStor organization is matched to the device's customer.
  • The device name in octoja matches the NovaStor node name (case-insensitive). The name must be unique both within the customer in octoja and within the NovaStor organization. Otherwise octoja does not link the node to a device.
  • To add the check, you need the Monitoring Check Management permission.

The octoja platform connects to DataCenter, not the agent. For a firewall or IP allowlist in front of your DataCenter API, see IP addresses and firewall rules.

Steps

  1. Open the device and, on its Checks tab, click Add Check → NovaStor backup.
  2. Adjust the thresholds if needed and click Add Check.

Alternatively, deploy the check with a config package.

Settings

FieldTypeRequiredDefaultDescription
Warning after (hours)NumberNo26Hours since a backup job's last successful run at which the job reports a warning
Critical after (hours)NumberNo50Hours since a backup job's last successful run at which the job reports a critical result

If the thresholds are entered the wrong way round, the check swaps them before evaluating. A negative threshold counts as an invalid configuration.

Results

The check evaluates each backup job of the linked NovaStor node separately:

Condition per jobSeverity
The most recent run failedCritical
One of the job's timestamps lies in the futureWarning
None of the last 20 runs succeededWarning
The last successful run has reached Critical after (hours)Critical
The last successful run has reached Warning after (hours)Warning
The most recent run neither succeeded nor failed (for example, it finished with warnings)Warning
The most recent run succeeded and is within the thresholdsOK

The overall result is the worst severity across all jobs. The thresholds already apply when the value is equal: with the default, a job warns from exactly 26 hours.

The check also reports a Warning when:

ConditionMeaning
The integration is not connectedNovaStor DataCenter is not set up
The device is not linkedNo NovaStor node matches this device, or the NovaStor organization is no longer matched to the device's customer
Synchronization failedoctoja could not retrieve the NovaStor organization's data during the last attempt
Synchronization is staleThe last successful synchronization is more than 90 minutes old or predates the current connection
The thresholds are invalidA threshold is negative
The node is disconnectedNovaStor reports the node as not connected. Its jobs are still evaluated
There are no backup jobsNo backup job is assigned to the node

Collected metrics

Per backup job:

  • Name and NovaStor status of the most recent run
  • Time of the most recent run and of the last successful run
  • Age of the last successful run in hours
  • The job's evaluated severity

Notes

  • The check reads only the data octoja has synchronized. Synchronization with NovaStor DataCenter also runs every 30 minutes, and additionally right after connecting and after saving the customer matches.
  • Only backup jobs are evaluated. Script, restore, retention, and cloning jobs do not count.
  • octoja reads the last 20 runs of each job from NovaStor. If the last successful run is older than that, the job reports a warning even if the age thresholds are set higher.

See also: Set up alerts for a check