Unitrends UniView Backup Health Triage
Overview
The morning backup check answers one question per customer: is every protected
system recoverable from last night? UniView sees every customer at once, so the
sweep is a handful of tenant-wide queries rather than a login per appliance.
All tools used here are plain reads in Conduit; none is admin-gated.
Anti-triggers
- "What does this customer protect at all?" (missing assets, Endpoint
Backup, SaaS coverage): use the
unitrends-uniview-protection-coverage skill.
- Microsoft 365 or Google Workspace backup failures: Spanning user status
lives in the
unitrends-uniview-spanning-saas-backup skill.
- Fixing a failure (rerunning a job, freeing storage, dismissing an alert):
the API is read-only. That work happens in UniView or on the appliance.
Key Concepts
| Signal |
Tool |
Filter |
| Failed backup |
unitrends_uniview_backups_list |
status: "Failed" plus a start_time_from window |
| Backup with warnings |
unitrends_uniview_backups_list |
status: "Warning" |
| Failed replication (offsite copy) |
unitrends_uniview_backups_list |
replication_status: "Failed" |
| Unresolved backup issue |
unitrends_uniview_backupiq_alerts_list |
type is required: alert, job, conditional or helix |
| Appliance down |
unitrends_uniview_appliances_list |
is_online: false |
| Appliance storage low |
unitrends_uniview_appliances_list |
total_mb_free_to: <MB>, or sort by total_mb_free |
Customer IDs in every result are UUIDs. Resolve them to names once with
unitrends_uniview_customers_list and reuse the map.
Common Workflows
Morning sweep (last 24 hours)
unitrends_uniview_customers_list (page through it) to build the
ID-to-name map.
unitrends_uniview_appliances_list with is_online: false. Do this
before reading failures: an offline appliance stops reporting jobs, so
its customers show no failures at all.
unitrends_uniview_backups_list with status: "Failed" and
start_time_from set to 24 hours ago, order_by: "start_time",
order_direction: "desc". Page through every page in paging.total_pages.
- Repeat step 3 with
status: "Warning", then with
replication_status: "Failed".
unitrends_uniview_backupiq_alerts_list with type: "alert" and
is_dismissed: false, then type: "job". Add severity: "critical" or
"alarm" to narrow when the queue is long.
unitrends_uniview_appliances_list sorted by total_mb_free ascending to
find appliances close to full. Compare free space with the appliance's
total size; a fixed MB threshold means different things on a 2 TB and a
60 TB appliance.
One-off failure or a real gap?
A single failed job that succeeded on its next run is noise. Repeated failures
are a protection gap. For each failed backup:
- Take its
asset_key and call unitrends_uniview_backups_list with that
asset_key, order_by: "start_time", order_direction: "desc",
page_size: 10.
- If the most recent run is
Successful, record it as self-healed.
- If the last two or more runs failed, or there is no successful run in the
last 48 hours, record it as a gap.
Ranking the queue
| Priority |
Finding |
| P1 |
Appliance offline; asset with no successful backup in 48 hours; repeated failures on the same asset; critical BackupIQ alert |
| P2 |
Single failure not yet retried; failed replication (the offsite copy is stale); appliance under ~10% free |
| P3 |
Warnings; self-healed failures; appliance version drift |
Report per customer, P1 first. Include the appliance (asset_tag), asset,
last successful run time and the job type for each line, so the technician can
go straight to the job.
Gotchas
- Silence is not success. An offline appliance or an asset removed from its
schedule produces no failed jobs. Check appliances first, and use the
unitrends-uniview-protection-coverage skill to catch assets with a stale last backup.
- Read every page. The server returns one page per call (default 50). A
sweep that reads only page 1 under-reports.
- Muted BackupIQ alerts are hidden by default. Pass
is_muted: "all" when
auditing why an alert never reached the queue.
InProgress jobs started in the window may still finish. Do not count
them as failures.
- Times are UTC ISO 8601. Convert the customer's backup window to UTC before
building
start_time_from.
- Rate limits are undocumented. Prefer tenant-wide filtered calls over one
call per customer. On a 429, wait the
Retry-After value.
Related Skills
1---2name: unitrends-uniview-backup-health-triage3description: >4 The cross-customer backup health sweep in Unitrends UniView: failed and warning5 backup jobs, failed replication, open BackupIQ alerts, offline appliances and6 low appliance storage, how to tell a one-off failure from a protection gap, and7 how to rank the findings into a technician work queue.8when_to_use: >-9 When a technician or NOC lead needs to know which customers' Unitrends backups10 failed or are at risk, typically as the morning backup check. Use when: failed11 backups, backup triage, morning backup check, uniview failures, replication12 failed, BackupIQ alerts, offline appliance, or appliance storage full.13metadata:14 source: https://skillmd.com/skills/wyre-ai/unitrends-uniview-backup-health-triage15---1617# Unitrends UniView Backup Health Triage1819## Overview2021The morning backup check answers one question per customer: is every protected22system recoverable from last night? UniView sees every customer at once, so the23sweep is a handful of tenant-wide queries rather than a login per appliance.24All tools used here are plain reads in Conduit; none is admin-gated.2526## Anti-triggers2728- **"What does this customer protect at all?"** (missing assets, Endpoint29 Backup, SaaS coverage): use the `unitrends-uniview-protection-coverage` skill.30- **Microsoft 365 or Google Workspace backup failures**: Spanning user status31 lives in the `unitrends-uniview-spanning-saas-backup` skill.32- **Fixing a failure** (rerunning a job, freeing storage, dismissing an alert):33 the API is read-only. That work happens in UniView or on the appliance.3435## Key Concepts3637| Signal | Tool | Filter |38|--------|------|--------|39| Failed backup | `unitrends_uniview_backups_list` | `status: "Failed"` plus a `start_time_from` window |40| Backup with warnings | `unitrends_uniview_backups_list` | `status: "Warning"` |41| Failed replication (offsite copy) | `unitrends_uniview_backups_list` | `replication_status: "Failed"` |42| Unresolved backup issue | `unitrends_uniview_backupiq_alerts_list` | `type` is required: `alert`, `job`, `conditional` or `helix` |43| Appliance down | `unitrends_uniview_appliances_list` | `is_online: false` |44| Appliance storage low | `unitrends_uniview_appliances_list` | `total_mb_free_to: <MB>`, or sort by `total_mb_free` |4546Customer IDs in every result are UUIDs. Resolve them to names once with47`unitrends_uniview_customers_list` and reuse the map.4849## Common Workflows5051### Morning sweep (last 24 hours)52531. `unitrends_uniview_customers_list` (page through it) to build the54 ID-to-name map.552. `unitrends_uniview_appliances_list` with `is_online: false`. Do this56 **before** reading failures: an offline appliance stops reporting jobs, so57 its customers show no failures at all.583. `unitrends_uniview_backups_list` with `status: "Failed"` and59 `start_time_from` set to 24 hours ago, `order_by: "start_time"`,60 `order_direction: "desc"`. Page through every page in `paging.total_pages`.614. Repeat step 3 with `status: "Warning"`, then with62 `replication_status: "Failed"`.635. `unitrends_uniview_backupiq_alerts_list` with `type: "alert"` and64 `is_dismissed: false`, then `type: "job"`. Add `severity: "critical"` or65 `"alarm"` to narrow when the queue is long.666. `unitrends_uniview_appliances_list` sorted by `total_mb_free` ascending to67 find appliances close to full. Compare free space with the appliance's68 total size; a fixed MB threshold means different things on a 2 TB and a69 60 TB appliance.7071### One-off failure or a real gap?7273A single failed job that succeeded on its next run is noise. Repeated failures74are a protection gap. For each failed backup:75761. Take its `asset_key` and call `unitrends_uniview_backups_list` with that77 `asset_key`, `order_by: "start_time"`, `order_direction: "desc"`,78 `page_size: 10`.792. If the most recent run is `Successful`, record it as self-healed.803. If the last two or more runs failed, or there is no successful run in the81 last 48 hours, record it as a gap.8283### Ranking the queue8485| Priority | Finding |86|----------|---------|87| P1 | Appliance offline; asset with no successful backup in 48 hours; repeated failures on the same asset; critical BackupIQ alert |88| P2 | Single failure not yet retried; failed replication (the offsite copy is stale); appliance under ~10% free |89| P3 | Warnings; self-healed failures; appliance version drift |9091Report per customer, P1 first. Include the appliance (`asset_tag`), asset,92last successful run time and the job type for each line, so the technician can93go straight to the job.9495## Gotchas9697- **Silence is not success.** An offline appliance or an asset removed from its98 schedule produces no failed jobs. Check appliances first, and use the99 `unitrends-uniview-protection-coverage` skill to catch assets with a stale last backup.100- **Read every page.** The server returns one page per call (default 50). A101 sweep that reads only page 1 under-reports.102- **Muted BackupIQ alerts are hidden by default.** Pass `is_muted: "all"` when103 auditing why an alert never reached the queue.104- **`InProgress` jobs** started in the window may still finish. Do not count105 them as failures.106- **Times are UTC ISO 8601.** Convert the customer's backup window to UTC before107 building `start_time_from`.108- **Rate limits are undocumented.** Prefer tenant-wide filtered calls over one109 call per customer. On a 429, wait the `Retry-After` value.110111## Related Skills112113- [api-patterns](../api-patterns/SKILL.md): headers, paging, truncation, errors114- [protection-coverage](../protection-coverage/SKILL.md): stale and missing protection