Backup Overview
Purpose: Whether the estate is actually protected, and what protecting it costs in capacity and time. Eight reports covering job outcomes, runtime, pool capacity, protection gaps, and a per-VM audit. Visual One reads the backup platforms rather than performing backups, so this section is assurance and capacity reporting, not a backup product.
What this section is, and what it is not
There is no scheduling, no restore, and no job control here. What the section provides is the answer to the question backup consoles are worst at: not did last night’s jobs run, but is everything that should be protected actually protected, across several backup platforms at once, with the evidence to prove it.
Because the reports read from multiple backup products in one place, terminology varies by source. Status values in particular may appear in the underlying platform’s own vocabulary rather than a normalized one.
The reports in this section
| Report | What it answers |
|---|---|
| VM Audit Report | Which virtual machines are protected, which have never been backed up, and which are replicated and immutable |
| Backup Status | How job outcomes are trending, and which jobs are erroring |
| Protection Gap Analysis | Which backup domains have coverage gaps |
| Backup Summary Trend | How backup capacity has grown, and how much headroom is left |
| Backup Pool Summary | How full each backup pool is right now |
| Backup Pool Trend | How a single pool’s capacity is moving |
| Backup Host Occupancy | How much each protected client contributes to backup capacity |
| Backup Runtime | Which jobs are slow, and which are getting slower |
The three questions the section answers
- Coverage. VM Audit and Protection Gap Analysis. Is anything unprotected. This is the audit question and the one with real risk attached.
- Capacity. Pool Summary, Pool Trend, Summary Trend, Host Occupancy. Will we run out of somewhere to put backups.
- Performance. Status and Runtime. Are jobs succeeding, and do they still fit in the backup window.
Coverage is the one to start with. A backup estate can show healthy job success rates and full pools while a significant number of systems have never been backed up at all, because a job that was never created cannot fail.
Common actions
A monthly review runs VM Audit filtered to never-backed-up systems, Status for the outcome trend, Runtime for jobs approaching the window, and Pool Summary for capacity pressure. Gap Analysis gives the domain-level picture to take into a governance conversation.
Tips
Backup job names, client hostnames, and pool names are among the most revealing strings in any environment. They routinely encode site names, application names, and compliance scope. Redact them before any screenshot from this section leaves the organization.
Related screens
Executive Backup Summary is the board-level rollup of this section, with coverage percentages by site. Snap / Replication Details covers array-based protection rather than backup software.