Note: Backups may not be offered for self-serve activation at launch. Check with your plan or account team for availability.
Alongside that, Backups is built to connect to each backup vendor using API credentials you supply. A sync worker pulls job data on a schedule (default: every hour per vendor) and normalizes it into a common job format. ⚠️ That third-party vendor path is built but not yet collecting — no tenant has a vendor configured and end-to-end collection has not been proven, so it feeds no jobs yet.
Two background detectors run every fifteen minutes:
- Missed backup detection — flags any device that has not had a successful job within its expected interval and creates a synthetic missed-job record.
- Failure-streak detection — triggers when a device records three or more consecutive failed jobs within 48 hours.
Both detectors can open a PSA ticket and page OnCall automatically.
Integration with RMM
Backups shares device and client context with the RMM product. Devices managed in RMM appear as backup targets in Backups, so coverage gaps are visible alongside endpoint health. The RMM service exposes its own legacy backup sub-routes (/api/v1/backups/jobs, /schedules, /restores) for historical reasons; those are separate from the The One Stack Backups service routes but serve the same coverage view.
Key Concepts
| Term | Meaning |
|---|---|
| Vendor | A backup software provider (Veeam, Datto, etc.) connected via API |
| Policy | Centralized rule defining schedule, retention, backup type, and expected interval |
| Job | A single backup run — scheduled, manual, or synthetic missed |
| Restore | A tracked request to recover data from a backup snapshot |
| Catalog | File-level metadata index across all backup sets |
| Coverage | Whether every device in scope had a successful backup in a given window |
FAQ
Is Backups the same as Defend? No. Defend (threat detection) is a separate product. Backups is the backup monitoring platform.
Does Backups replace the backup vendors themselves? No. Backups monitors them from a single pane, but it does not replace them. For a workload Backups captures itself (endpoint files and folders), the backup data is written into the platform's own object storage. For a connected third-party vendor, the data stays in that vendor's storage and Backups reads job status from the vendor API. Restores run through the platform's own paths — the endpoint agent for files, and the SQL and image paths for those workloads — never through a vendor API.
What happens if the vendor API is unavailable? The last successful sync data remains visible. The vendor record shows the last sync error message so you can act on it. When the vendor API is restored, click Sync Now on the vendor to pull the latest data immediately.