Skip to main content

Back up a device in Backups

Updated

Overview

A protected device is an endpoint or server whose backups Backups is actively watching and managing. The All Devices page (and the per-client Device Protection view) is where you see protection status across the portfolio: which devices have a current backup, which are behind, and which aren't protected at all. Protecting a device means it has a backup policy/source feeding job data into Backups.

How To: See Protection Status

  1. Open Backups → All Devices (/backups/devices) for the whole fleet, or Backups → Device Protection for the protection-focused view.
  2. Each device shows its protection state and last successful backup.
  3. Filter to find unprotected devices or devices with no recent successful job.

How To: Bring a Device Under Protection

  1. Confirm the device's backup source is connected — endpoint / endpoint-data backup, or a SaaS connection for cloud accounts. A vendor connection (Veeam/Datto/Acronis/etc., configured under Settings) is also supported, but ⚠️ that third-party monitoring path is built but not yet collecting — no tenant has a vendor configured and end-to-end collection is unproven — so it feeds no jobs yet.
  2. Make sure the device is mapped to the right client so its jobs land in the right place.
  3. Assign or confirm a backup policy (schedule, retention, expected interval) so the missed-backup detector knows when to flag it.
  4. Once jobs flow in, the device shows as protected with a healthy last-backup time.

How To: Find Coverage Gaps

Open Backups → Coverage Gap (/backups/coverage), pick a window (30/60/90 days), and review every device with no successful backup in that window. From there, fix the source/policy or open a PSA ticket. This is the fastest way to catch a device that silently stopped backing up.

Troubleshooting

A device shows unprotected but should be covered. Confirm its backup source (vendor connection or SaaS connection) is syncing and that the device is mapped to the correct client — an unmapped device's jobs won't attach to it.

Last-backup time is stale. The source ran but the sync hasn't pulled it yet, or the job actually failed. Check the Jobs page for the device's recent runs.

Related