Supported software

It reads the reports your backup software already sends.

BackupSentinel does not connect to your backup servers. It matches the notification emails they send to a job by job name, and anything else can report with one HTTP request.

Start free trial Setup steps

Ten products are read out of the box.

Each rule knows the subject lines and wording of one product: which words mean Failed, which mean Warning, and where the job name and backup size sit. Point the product at the client address and each report is matched to a job by its name.

01Veeam B&ROpen Veeam Backup & Replication → main menu → Options → E-mail Settings.Setup steps
02Synology DSMIn DSM 7.2 or later, open Control Panel → Notification → Rules and add a rule with only the Hyper Backup backup results ticked.Setup steps
03Acronis Cyber ProtectOpen the protection plan you want to monitor → Settings.Setup steps
04Microsoft 365In the Exchange admin center, go to Mail flow → Rules and create a rule that forwards a copy of your backup report emails to the client address.Setup steps
05Proxmox PBSIn Proxmox VE 8.1 or later, go to Datacenter → Notifications, add an SMTP target with the address as recipient, and a matcher that sends backup notifications to it.Setup steps
06DuplicatiEdit the backup → Options → Advanced options.Setup steps
07NAKIVOGo to Settings → General → Email Settings and set up your SMTP server.Setup steps
08DattoCheck your Datto Partner Portal's notification settings for the device or backup job.Setup steps
09MSP360Open the backup plan's settings and look for its email notification option.Setup steps
10Cove Data ProtectionIn the Cove management console, open the device or backup profile's Notifications tab.Setup steps

Any other product

Anything that sends email falls back to keyword matching: failed, failure or error means Failed, warning means Warning, success or “completed successfully” means Healthy. When that is not enough, write a custom rule with a subject pattern, keyword lists and field patterns, and test it on a real email before saving.

Custom rules

Four places an alert can go.

One open alert per job. A warning that becomes a failure escalates the same alert; the next OK report closes it and sends a recovery notice on every channel it reached. Each channel has a Send test button.

Failed deliveries are retried every 10 minutes. SMS is not available.

Email: Alerts and recovery notices to any address you enter.
Slack: An incoming webhook on hooks.slack.com. Paste the webhook URL; alerts post to the channel it belongs to.
Microsoft Teams: A Workflows webhook. Paste the URL from the workflow that posts to the team channel.
PagerDuty: Events API v2 with auto-resolve. An OK report resolves the incident the alert opened.

For anything that does not send email.

A script that copies a database dump, a product with no notification setting, a cron job on a server you do not want sending mail: each can report its result with a single request. The job then follows the same cadence, grace and alerting as a job fed by email.

One POST per run with a status of ok, warn or failed
An Idempotency-Key header makes retries safe: a repeat is acknowledged, not counted twice
Optional size_bytes and timestamp feed the same jobs table, heartbeat and reports
Keys start with bsk_live_, are revoked in Settings, and allow 60 requests per minute each

Report API reference

POST https://app.backupsentinel.io/api/v1/jobs/{jobId}/report
Authorization: Bearer bsk_live_…
Idempotency-Key: nightly-2026-10-02
Content-Type: application/json

{"status": "failed",
  "size_bytes": 48318382080,
  "timestamp": "2026-10-02T01:12:40Z"}

# 200
{"ok": true, "status": "failed",
  "alert_id": "…", "duplicate": false}

# 429 when over 60 requests/minute

Add one recipient address. That is the whole setup.

Create a client, copy its address into the backup software, and the next report starts monitoring. The trial runs 14 days with no card.

Start free trial Sign in