Monitoring and analytics of the data platform: capacity, anomalies and the question that counts — “are we really protected?”
Veeam ONE watches the watchman: it monitors the backup infrastructure (and the virtual one underneath), computes the protection SLAs (which machines do NOT have a valid copy?), forecasts the repositories' saturation and flags the suspicious behaviors — like the jobs suddenly growing, the classic symptom of encryption in progress.
The gap between 'estate' and 'protected' highlighted every morning: the new machine doesn't slip away.
The ONE alarms inside Yocto Vision: the failed job is a ticket, not a lost email.
Repositories and windows observed over time: the purchases planned with charts.
Protection SLAs and verifications documented: NIS2 and insurers served.
Veeam ONE observes backup and virtualization: the predefined alarms (300+) flag failed jobs, breached RPOs, repositories running out and anomalies (the suspicious activity like massive encryption fires the ransomware alarm), the reports certify the protection (who's covered, who's not, at what RPO) and the capacity planning forecasts when the storage runs out; the Intelligent Diagnostics reads the VBR logs and suggests the known fixes.
The data platform with the numbers in hand.
The proofs of protection, generated by themselves.
The encryption anomaly seen from the copies' side.