---
name: feedback_backup_targets_never_guessed
description: Backup targets are a deliberate per-client decision - never infer which machine needs backup or deploy backup jobs from billing counts
metadata:
  type: feedback
---

When reconciling billed backup lines (e.g. Syncro "Service - Data Backup" qty) against
machines actually backing up (MSP360/B2), a mismatch is a BILLING question for Mike/Winter,
never a deployment instruction. (Howard, 2026-07-05, GPS->RMM audit backup verification.)

**Why:** which machine gets backed up is a deliberate choice made per client (usually the
server or a specific data machine) — billed qty does not mean "N machines each need a
backup job." Guessing targets and adding backup jobs would burn storage and misrepresent
what the client agreed to.

**How to apply:** report mismatches (billed > running, running > billed, dead buckets) as
findings with evidence; route the decision to Mike/Winter/client. Only configure a backup
job when the target machine is explicitly named by the user/client. Related:
[[project_av_migration_bitdefender_to_edr]] (the AV migration IS deploy-everywhere, unlike
backup — don't conflate the two postures).