Backup Radar: every backup job's latest result and SLA state

Backup Radar is ScalePad's backup monitor: it watches the backup jobs across whatever tools your team runs — the appliance, the cloud service, the Microsoft 365 backup — and judges each one against the service level you set for it. This connector reads that judgment into Current, per partner, so an account manager can answer "are their backups working" from the company record instead of opening a second console. One ScalePad Hub API key covers it, and Current only ever reads.

1. 1
   1 · Sign in to ScalePad Hub as an administrator

   Only a ScalePad administrator can create an API key. The key is personal — it carries the permissions of whoever made it — so that person has to stay an active admin for this feed to keep reading.
2. 2
   2 · Open your profile ▸ API Keys ▸ Create

   The keys live on your own Hub profile rather than under an account-wide setting.
3. 3
   3 · Copy the key before you leave the page

   ScalePad shows it once. The default expiry is two years, set at creation; put that date somewhere you will see it, because an expired key is refused exactly the way a revoked one is.
4. 4
   4 · Check the account has a Backup Radar subscription

   One key spans every ScalePad product the account is licensed for. Without a Backup Radar subscription the key is valid and still reads nothing — see the note below Test connection.

1. 1
   Open the Backup Radar card

   In Current's left sidebar open Integrations (it sits under Admin, so Tenant Admins have the link) and find Backup Radar under Backup & continuity, beside Datto Backup.
2. 2
   Paste the key, then press Test connection

   Current sends the key as the x-api-key header and makes one live read against Backup Radar before it stores anything. If ScalePad refuses, the card shows ScalePad's own reason rather than a generic failure. On success the key is stored server-side only — the browser never sees it again.
3. 3
   Let the first sync run

   The first pass writes a mapping row for every ScalePad client it finds before it walks the jobs, so the mapping panel fills in while the job walk is still going.

Backup Radar syncs every 6 hours on a schedule, plus whenever a Tenant Admin presses Sync now on the card. Each pass re-reads the monitored jobs with their latest results and refreshes the compliance history. A very large estate can also spill past a single sync pass — the counts simply keep growing until the next pass finishes the walk. Separately, one partner's card counts up to 1,000 jobs and lists the worst 100: a partner with more than 1,000 monitored jobs shows a + on the counts, and that + is a floor, not a total that will settle.

Current calls three read endpoints on ScalePad and nothing else: the per-partner compliance history, the monitored-job list, and — where the account is licensed for it — the ScalePad client list used for matching. Every request is checked against that list in code before it is sent. Backup Radar's own product can create and mute tickets, acknowledge failures, and edit backup methods and SLA policies; none of those paths exist in the connector, so they are unreachable rather than merely un-called. Creating, rotating, and revoking a key happens in ScalePad Hub, never from Current.

Backup Radar groups jobs by ScalePad client, and Current links each client to one of your companies in two passes. Where your PSA is connected to ScalePad, a client ScalePad imported from Autotask carries that Autotask company id, and Current matches on the id — no name involved. Everything else matches by normalized name: lowercased, with punctuation and Inc/LLC/Ltd-style suffixes stripped, and linked only when exactly one of your companies matches. Two that both fit stay unmapped for you to decide. The id pass needs a paid ScalePad product on the account; without one it is skipped and name matching still runs.

1. 1
   Work the Unmapped tab

   Integrations → Backup Radar → Manage opens on the clients the matcher could not place, and the card carries a count of them.
2. 2
   Map a client to its company

   Press Map on a row, type a few letters of the Current company, and pick it. That client's jobs attach to the company right away rather than waiting for the next 6-hour sync.
3. 3
   Ignore internal or test clients

   For a client that should never map to a company — your own internal backups, a lab — press Ignore. It moves to the Ignored tab and stops counting against the card's unmapped badge; Un-ignore brings it back.
4. 4
   Fix a wrong match later

   The Mapped tab lists every linked client and Unmap corrects a bad auto-match. A mapping you set by hand is never overwritten by a later auto-match, and neither is a manual unlink.

• ＋The company record: the Backup band opens for any partner Backup Radar watches, and a compact Backup Radar card sits beside it — jobs monitored, failing now, the share in SLA, and a worst-first list of jobs with each one's device, job name, classification, latest result, and SLA state.
• ＋The Backup & continuity chapter of a Strategic Business Review: the monitored-job counts and the compliance trend, read as a theme rather than a vendor name.
• ＋The backups-failing alert on the company: a job whose latest result is an error, or whose SLA reads Out Of Compliance (which includes Out Of Compliance - No Results), counts as failing. It is the same alert Datto Backup feeds, so a company gets one alert whichever tool saw the failure.
• ＋The "Backups failing now" tile on dashboards. Where both products are connected the two numbers are added and the tile says so on its face, because Datto counts protected systems while Backup Radar counts jobs.