CLIENTS & JOBS

Adding what you're watching

Every backup BackupWatch tracks belongs to a Job, and every job belongs to a Client. Set up the client once, then add one job per backup you want monitored for them.

Clients

A client needs a name and its email identifiers — the sender address(es) or domain that identify its mail. Each identifier is one of:

  • An address (contains @) — matches if it appears in the From address, e.g. veeam@client.com.au.
  • A domain — matches the sender's domain, a parent of it, or anywhere in the From address, e.g. client.com.au.
  • A subject token — for vendors that send from one shared address across all their customers (DropSuite always sends from support@dropsuite.com), use the client's name as it appears in the subject line instead of an address.
Clients list and Add client form
Clients — the client list and Add client form

Jobs

A job has a vendor (Veeam, DropSuite, or other), a target label (free text, e.g. "NAS + Wasabi"), and a schedule:

FrequencyFields
DailyExpected by time (HH:MM) + grace hours — a nightly backup expected by, say, 06:00 with a 4-hour grace window.
IntervalEvery N minutes, within an active window (e.g. 07:00–20:00), grace in minutes, optionally restricted to specific weekdays — for backups that run hourly during business hours.

Each client page shows a 30-day stacked history chart of that client's backup outcomes, and the Add job form sits right below it.

Client detail page with 30-day history and Add job form
A client page — 30-day history, jobs, and the Add job form

Match rules

A job only picks up mail once it has at least one match rule — a job with no rules can never auto-match, by design. Rules are covered in full on the How Matching Works page; the short version: add one precise manual rule per job (e.g. subject contains a distinctive phrase), and let the learning engine add more as you triage the Review queue.