Vigilio / Know When a Scheduled Backup Fails to Run
Vigilio monitoring guide

Know When a Scheduled Backup Fails to Run

A successful backup or scheduled task calls a unique Vigilio heartbeat URL. If the expected signal does not arrive on time, Vigilio records the incident and sends an operational alert.

Start monitoring for freeView pricing

How backup heartbeat monitoring works

A heartbeat monitor reverses the usual monitoring model. Vigilio does not need to connect to the backup application. Instead, the backup script calls a unique URL only after successful completion. Vigilio expects that signal on schedule.

  1. Create a heartbeat monitor in Vigilio.
  2. Copy its unique heartbeat URL.
  3. Add the URL call to the successful end of the backup script.
  4. Set the expected schedule and grace period.
  5. If the signal is missed, Vigilio creates an incident and sends a Telegram alert.
Best practice: call the heartbeat only after the backup command has completed successfully. Do not place it unconditionally at the beginning of the script.

PowerShell example

Call the heartbeat after the backup command returns a successful exit code:

& "C:\Backup un-backup.exe"
if ($LASTEXITCODE -eq 0) {
  Invoke-WebRequest -Uri "https://vigilio.online/heartbeat/YOUR_TOKEN" -UseBasicParsing
} else {
  exit $LASTEXITCODE
}

Batch file example

@echo off
"C:\Backup un-backup.exe"
if errorlevel 1 exit /b %errorlevel%
curl.exe -fsS "https://vigilio.online/heartbeat/YOUR_TOKEN"

Linux or cron example

The monitored machine does not need the Vigilio server agent for a simple heartbeat:

#!/bin/sh
/usr/local/bin/run-backup && \\
  curl -fsS "https://vigilio.online/heartbeat/YOUR_TOKEN"

rclone example

rclone sync /data remote:backups/server-01 && \\
  curl -fsS "https://vigilio.online/heartbeat/YOUR_TOKEN"

What heartbeat monitoring can and cannot prove

Heartbeat confirmsHeartbeat does not automatically confirm
The script reached the heartbeat step on time.That every backed-up file is valid and restorable.
The scheduler launched and completed the scripted workflow.That retention, encryption and off-site storage are correct.
A missed schedule can trigger an incident.That a restore test has succeeded.

Combine heartbeat monitoring with backup software logs, storage checks and regular restore tests.

Good heartbeat use cases

  • Nightly PowerShell backups.
  • Windows Task Scheduler jobs.
  • Database dump scripts.
  • rclone synchronization.
  • cron jobs and maintenance scripts.
  • Report generation and data-import jobs.

Monitor it with Vigilio

Create an account, add an external check or install the Windows agent, and receive Telegram alerts for operational incidents.

Start for freeAsk a question

Related monitoring pages

Windows Server monitoringCPU, RAM, disk and online/offline visibility. RDP login monitoringTrack Windows login, logout and source IP events. Backup heartbeat monitoringDetect missed backup jobs and scheduled tasks.
FAQ

Frequently asked questions

No. Any system or script that can make an HTTPS request can call a heartbeat URL.

Call it only after the important job has completed successfully. Use exit-code or exception handling so failed jobs do not send a success heartbeat.

A missed heartbeat shows that the expected success signal did not arrive. The backup application or script logs are still needed to determine the cause.

Yes. Add the heartbeat request to the successful end of the cron command, shell script, PowerShell script or scheduled task.

No. Heartbeats monitor job execution. Regular restore tests are still required to prove that backups are usable.