A status check across 169 monitored devices with 175 TB of protected storage. Flags devices with backup failures, missing data, and storage concerns. Generated by AI via Proxuma Power BI MCP server.
A status check across 169 monitored devices with 175 TB of protected storage. Flags devices with backup failures, missing data, and storage concerns. Generated by AI via Proxuma Power BI MCP server.
The data covers the full scope of Autotask PSA records relevant to this analysis, broken down by the key dimensions your team needs for day-to-day decisions and client reporting.
Who should use this: NOC teams, service managers, and MSP owners monitoring backup compliance
How often: Daily for operations, weekly for management review, monthly for client reporting
A status check across 169 monitored devices with 175 TB of protected storage. Flags devices with backup failures, missing data, and storage concerns. Generated by AI via Proxuma Power BI MCP server.
EVALUATE ROW("TotalOrgs", COUNTROWS('BI_Backup_SaasProtection_Backup_Stats'), "ActiveServices", SUM('BI_Backup_SaasProtection_Backup_Stats'[active_services_count]), "WithRecentBackup", SUM('BI_Backup_SaasProtection_Backup_Stats'[active_services_with_recent_backup_count]))Current state of all monitored backup devices
| Status | Devices | % of Total | Action |
|---|---|---|---|
| Recent Backup (OK) | 157 | 92.9% | |
| Backup Issues | 19 | 11.2% | |
| No Backup Data | 224 | — |
EVALUATE
SUMMARIZECOLUMNS(
"Status", BI_NAble_Device_Statistic[backup_status],
"DeviceCount", COUNTROWS(BI_NAble_Device_Statistic),
"PctOfTotal", DIVIDE(COUNTROWS(BI_NAble_Device_Statistic), [NAble - Total Active Devices])
)Protected storage across the device fleet
175 TB of protected storage spread across 169 devices averages out to roughly 1 TB per device. That average is useful as a baseline, but it hides the spread. A handful of file servers or database hosts likely account for a large portion of that total, while workstations sit well below 100 GB each.
Any device pulling significantly more than 2 TB should be flagged for review. Those are likely servers that need their own retention policies, offsite replication schedules, and storage growth monitoring. Without that separation, a single server's growth can eat into the backup window for the rest of the fleet.
EVALUATE
ADDCOLUMNS(
TOPN(20,
SUMMARIZE(BI_NAble_Device_Statistic, BI_NAble_Device_Statistic[device_name]),
[NAble - Total Protected Storage GB], DESC
),
"ProtectedGB", [NAble - Total Protected Storage GB]
)A 92.9% success rate is solid, but it means 12 devices failed their last backup. In a disaster scenario, those 12 devices have no recovery point. If even one of them is a domain controller, a file server, or an SQL host, the impact goes from inconvenient to business-critical.
The 224 devices without backup data is the bigger concern. These are devices that either never had backup configured or where the agent stopped reporting. Each one is an unprotected endpoint. Until those devices are accounted for, the 92.9% figure only tells part of the story.
175 TB of protected storage across 169 devices averages about 1 TB per device. Check whether any single device accounts for a disproportionate share. A server pulling 20 TB on the same schedule as a laptop pulling 50 GB will eventually cause backup window conflicts, especially if bandwidth is limited.
Each one is a potential data loss incident. Cross-reference against N-able RMM to determine whether these devices should have backup installed, were decommissioned, or are simply misconfigured. Prioritize servers and shared workstations.
Check error logs for common patterns: full disk, expired licenses, agent crashes. Group them by error type. If multiple devices share the same failure reason, fix the root cause once rather than troubleshooting each device individually.
Maintain this by setting up alerting on any device that misses two consecutive backup windows. Catching failures after one miss gives you time to fix it before the next scheduled run. Two consecutive misses should trigger a ticket automatically.
A device that completed its last scheduled backup job without errors. Partial completions or jobs that finished with warnings are not counted as successful.
These are devices in N-able RMM that have no backup statistics. The backup agent may not be installed, may have been uninstalled, or may have stopped reporting. They require manual review to determine the correct course of action.
Backup statistics sync through Proxuma Power BI, typically refreshed daily. The exact refresh time depends on the data pipeline schedule configured in your environment.
Connect Proxuma Power BI to your PSA, RMM, and M365 environment, use an MCP-compatible AI to ask questions, and generate custom reports - in minutes, not days.
See more reports Get started