Of the 47 in-scope LPARs owned by EAST or WEST, 57.4% have a current backup — but that headline number hides a sharp split: WEST is effectively fully covered while EAST carries the overwhelming majority of the exposure.

Fig. 1.1 Backup coverage by owner. EAST’s 29.6% coverage (cyan) reflects 19 LPARs with no backup_server recorded at all — not a slow or failing job, but no job configured. WEST’s 95.0% coverage (green) is healthy, split across two backup servers.

Level two of the rollup — each owner split by whether the LPAR’s most recent backup is current.

Fig. 3.1 Backup coverage vs. an 80% target. EAST sits 50.4 points below target; WEST exceeds it.

The master comparison list is the filtered population itself — every LPAR returned by backup_vm_audit_report_proc for this client and period where the Owner tag equals EAST or WEST and the Custom Tag (Application ID) is populated.

backup_vm_audit_report_proc returned 2,051 total LPAR/VM records for this client and period. Of those, 168 carry an Owner tag of EAST or WEST, and 47 of that group also carry a non-blank Custom Tag (Application ID) — this 47-record set is the audit population used throughout this report. The remaining 1,883 records have no Owner tag populated and fall outside EAST/WEST ownership scope.

“Backup Current” reflects the proc’s own last_backup_status field (Yes/No) rather than a derived threshold — VisualOne already evaluates recency against the client’s configured backup SLA. “Backup Server” is the backup_server_name field; LPARs with no current backup uniformly show no backup server assigned, meaning the gap is a missing or unconfigured job rather than a failing one.