Named backup coverage for known servers
Every server should be covered by a named backup product — a server visible to RMM with no backup coverage on record is the single most expensive gap a BCDR runbook can have.
Interpret the result in context
Backup-product coverage is an inventory check. It does not establish job success or restore readiness, which should be reviewed separately.
Configure the expectation.
Use this baseline as a starting point. You can also build your own controls and standards from integration data, with client-specific requirements and documented exceptions.
A fixed baseline expectation
This shipped control has no adjustable numerical threshold. Review its applicability and record approved exclusions for the client.
Review. Remediate. Verify.
Use one-click remediation where the integration and action support it, or the evidence to guide the technician’s next step.
- 01
Match the server inventory to the backup platform’s protected workloads.
- 02
Assign the approved backup policy where coverage is missing.
- 03
Verify the mapping, a successful run and the agreed restore-testing process.
A completed action is only part of the record. Refresh the supporting evidence to establish whether the finding has cleared.
Make your baseline part of every client review.
Connect checks, findings and remediation to the same client record.