research

Measuring the share of devices missing a completed backup check

A measurement method that separates a successful backup job from a completed restore check and reports coverage for critical systems.

Short answer

Use this benchmark to size repeatable IT work, set the review cadence, and decide what stays with the technical owner before assigning the workflow to an IT virtual assistant.

Research playbook

MeasureVolume and handling time
OwnerTechnical manager validates
Risk ruleName sensitive access
RefreshQuarterly benchmark review
On this pageJump to section

Key stats

PopulationBackup inventoryStudy protocol
Check evidenceRestore recordStudy protocol
Report groupsType and criticalityStudy protocol

Key takeaways

A backup schedule and a restore record are different controls, and many teams can show only the first. The job ran, the storage filled, and the report turned green, but no one opened the files. This study measures the share of devices and systems with a completed restore check inside the review period. It gives the IT owner a way to see coverage without reading every job log.

Question and scope

The study asks what share of in-scope systems has at least one completed restore check in the review period. The unit is one system or device with a backup policy, such as a server, a laptop, or a cloud workspace. The population is the backup inventory for the chosen business unit. The result describes that inventory and period, not the reliability of the backup product in general.

Exclude systems with no backup policy, because the question is about checks rather than backup design. Record them separately as an exposure count. Include cloud services where the vendor provides the backup but the company owns the restore test. The scope should name the systems the team can test with its current access.

Define a completed check

A check is complete when someone restored data to a test location and confirmed that it opened or ran. A successful backup job is not a check, and a storage report is not a check. Record the restore point, the person, the date, and the evidence. The definition should be strict enough that a green dashboard cannot satisfy it.

Decide whether a partial restore counts, such as a sample folder from a large file server. Allow it only when the sample covers the data the owner cares about and the method is written down. Keep the same rule for every system in the period. A changing definition makes the coverage number move for reasons unrelated to the work.

Build the device frame

Export the backup inventory from the management console and the asset register. Reconcile the two lists so a device is not counted twice or missed. Add the system owner, the backup policy, and the last successful job date. The frame should show which systems are protected by an agent and which rely on a cloud service.

Mark the systems that hold regulated or business-critical data, because they need a stricter check cadence. Note the systems that were added or retired during the period. If a system changed owners, use the owner at the end of the period for the report. The frame is a snapshot, so record the date it was taken.

Sample and verify

If the population is large, take a random sample across system types and owners. Pull the restore record for each sampled system and compare it with the backup job history. Look for a check that was logged but has no evidence file. A log entry with no restore output is a claim, not a completed check.

Ask the owner to confirm the last check and the result. If the owner cannot recall it, mark the check as unverified and show it separately. Do not replace a missing record with a verbal assurance for the coverage calculation. The point of the measure is to find the gap between confidence and evidence.

Calculate the missing share

Count the systems with a completed check and divide by the systems in scope. Report the missing share and the count, then split the result by system type and criticality. A high coverage rate on laptops can hide a missing check on the finance database. The critical group should always appear on its own line.

Show systems with no backup policy beside the missing checks, because the fixes are different. Add the age of the oldest completed check for each critical system. A system checked once a year may be technically covered and still fail a monthly recovery target. Report the cadence with the coverage.

Compare with recovery targets

Find the written recovery point and recovery time objectives for each critical system. Compare the last restore point with the recovery point objective and the test duration with the recovery time objective. A backup can pass a coverage check and still miss the target that matters in an incident. Report both results side by side.

If no objective exists, propose one from the business impact and record the proposal. Note the systems where the owner has accepted a longer recovery time. Record that decision with the date and the reason. An accepted risk is a management choice, not a gap in the audit.

Report to owners

Send each owner a short list of their systems, the last completed check, and the missing evidence. Include the recovery target and whether the system meets it. Ask for a retest date for the systems with no check. Keep the report at the system level rather than the person level.

Give the IT manager a summary with the coverage rate, the critical gaps, and the oldest successful restore. Add one example of a check that found a real problem so the work is not treated as paperwork. Ask for a decision on the systems that remain uncovered. The report should lead to a scheduled retest, not a general reminder.

Limits and next use

The study counts checks that have a record and a person who can confirm them. It does not prove that a full recovery would work under incident pressure or that the restored data is complete. It also cannot see a restore performed by a vendor without a shared record. State those limits when the result is presented.

Repeat the measurement after the check process changes and compare the same system groups. If coverage rises but critical gaps remain, the next fix is the schedule rather than the tool. Keep the frame and the evidence with the report so the next reviewer can rerun it. Coverage becomes a control when the team reviews it every quarter.

Check the restore evidence

Open the evidence file for a sample of completed checks and confirm that it shows the restored data, not only the backup job. Look for a timestamp, a file listing, and a note from the person who verified it. A screenshot of a progress bar is not proof that the restore finished. Reject evidence that cannot answer what was restored and when.

Ask whether the test used the same recovery process the team would use in an incident. A restore performed with an administrator's local tool may not prove that the documented steps work. Note any step that required knowledge held by one person. The check should test the runbook as well as the backup.

Use the result with the incident plan

Add the coverage result to the incident response plan and the next recovery exercise. A system with no completed check should be named in the exercise rather than left on a dashboard. Give the exercise a scenario that uses the real recovery time objective. The team learns more from one timed restore than from a monthly percentage.

Review the result with the business owner of each critical system, not only with IT. Ask whether the recovery target still matches how the business uses the system. Record any change to the target and the date it takes effect. Coverage and recovery planning should move together.

Set the check cadence

Set the check cadence from the recovery objective and the rate of change in the system. A system that changes daily may need a monthly check, while a stable archive may need one every quarter. Write the cadence beside the system in the inventory. A single annual schedule for every system is easy to publish and hard to defend.

Put the next check date in the calendar and assign the person who will run it. If the check depends on a vendor, confirm the vendor's test window before booking. Record the date the result was reviewed, not only the date the test ran. The cadence is working when the oldest check stays inside the stated interval. Publish the cadence where the system owner can see it.

Sources and next step

Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the renewal, shared account, backup, asset register, and access ticket controls discussed here. The NIST SP 800-53 Rev. 5 supports the account and audit record checks, and the GAO data reliability guidance supports the sampling and verification approach used in these methods. Apply your own policies, contracts, and system documentation when adapting the method.

Compare this study with the shared account ownership audit and the backup check coverage study before combining them into one review cycle. If the measurement work is recurring and your technical owner can define the scope, review the service areas and contact ITVirtualAssistant to discuss a limited pilot.

Benchmark brief

What this research page must produce

Working number

A practical estimate for volume, review time, escalation rate, and assistant capacity.

Operating boundary

A clear split between routine support, preparation work, and technical ownership.

What the measuring the share of devices missing a completed backup check data shows

Treat this as a planning benchmark, not a universal number. Compare the benchmark against your ticket volume, SaaS stack, documentation backlog, and support risk before assigning recurring work.

The useful output is a decision about capacity, not a static statistic. If the workflow is high volume and low judgment, an IT virtual assistant can absorb coordination and upkeep. If the workflow is low volume but high risk, keep it with the technical owner and use the assistant only for preparation, reminders, and documentation.

Workflow

Recommended operating workflow

1

Collect a baseline

Pull the last 30 to 90 days of examples related to measuring the share of devices missing a completed backup check, including completed work and unresolved exceptions.

2

Classify the work

Tag each item by routine admin, manager approval, technical decision, security risk, or vendor dependency.

3

Set the operating number

Use the median weekly volume and review time to decide how many assistant hours the workflow deserves.

4

Refresh the benchmark

Recheck the numbers quarterly so tool growth, new systems, and security requirements do not silently change the scope.

Decision rules

MetricUse it to decideManager action
Weekly volumeWhether the workflow is worth assigning as recurring assistant work.Approve a weekly capacity target and backlog threshold.
Access sensitivityWhether the assistant can work directly or only prepare review notes.Set least-privilege permissions and removal dates.
Escalation rateWhether the workflow is stable enough to delegate.Rewrite the SOP when exceptions exceed the agreed threshold.

Consolidated statistics

StatisticFigureSource
PopulationBackup inventoryStudy protocol
Check evidenceRestore recordStudy protocol
Report groupsType and criticalityStudy protocol

Sources

  1. NIST SP 800-34 Rev. 1, Contingency Planning GuideRecovery objectives, backup planning, and test documentation for information systems.
  2. CISA Cyber EssentialsPractical backup and recovery guidance for small and mid-sized organizations.
  3. NIST Cybersecurity Framework 2.0Data security and recovery planning outcomes for critical services.
  4. CISA Cross-Sector Cybersecurity Performance GoalsBackup, recovery, and incident response goals used to frame the check cadence.

Measurement checklist

FieldWhat to captureOwner
VolumeWeekly request count, backlog age, and repeat issue patternsAssistant prepares, manager reviews
RiskAccess level, customer impact, security sensitivity, and approval needsTechnical owner
CadenceDaily, weekly, monthly, or quarterly review rhythmManager
EvidenceSample tickets, logs, screenshots, and before-after examplesAssistant collects, owner validates
EscalationTriggers, approval path, response time, and stop-work rulesTechnical owner

How to read the result

A good research page should leave the manager with a working number and a clear boundary: what the assistant can do every week, what the assistant can prepare for review, and what must never move without the accountable technical owner.

Source and refresh note

This planning page is dated for 2026 and should be refreshed quarterly as tool stacks, ticket patterns, and security expectations change.

How should teams use this benchmark?

Use it to define task volume, access limits, review cadence, and escalation rules before assigning work.

Get free benchmark review