Skip to main content
Migration Notice
We're migrating documentation from the old portal into this one. Some things may look a little different or out of place in the meantime — we know, and we're working to get it right. If something's unclear or doesn't look right, let us know.

Group Health

This tab provides a per-group summary of RPO (Recovery Point Objective) compliance across all protection groups. Use it to get an immediate read on which groups are meeting their protection targets and which need attention, without having to drill into individual bucket changelists.

Overview​

Each protection group is represented by a card in a responsive grid (3 columns on wide screens). The card aggregates the sync state of every vault config in the group and expresses the result as a single RPO status based on the group's configured RPO target (in hours) and the time elapsed since the most recent successful sync (the lag).

The header strip above the grid shows four summary counters:

  • Total Groups — the number of groups returned by the dashboard.
  • Compliant — count with rpoStatus = compliant.
  • At Risk — count with rpoStatus = at_risk.
  • Breached — combined count of breached + unknown (no sync has ever occurred is also surfaced here).

Card Fields​

Group name — the name of the protection group as defined in Source Data Protection Group Config. If the group has a color set, it appears as a left border on the card.

RPO target (hours) — shown immediately below the name as RPO: Nh. This is the maximum acceptable lag for the group.

Status badge — one of:

  • Compliant (emerald) — lagHours is within the RPO window. The most recent successful sync is fresh enough.
  • At Risk (amber) — lag is approaching the RPO window (backend-defined threshold; typically 80 % of the RPO).
  • Breached (red, with warning icon) — lag exceeds the configured RPO hours. Data protection is past the target. The card also gains a red border.
  • Unknown (gray, shield icon) — no successful sync has been observed yet for any config in the group.

Bucket counts row — shows total buckets in the group, the number currently protected (green), and any unprotected count (amber). Helps identify groups with buckets that have no completed copy yet.

Last sync — a human-friendly lag expression (< 1h ago, 3.2h ago, 1.4d ago, or Never synced). Colored by status — emerald when compliant, amber at risk, red when breached.

RPO progress bar — a horizontal bar where 100 % = lag equals the RPO target. The bar is emerald when compliant, amber when at risk, red when breached, gray when unknown. The numeric lagHours / rpoHours is shown below the bar for precise reading.

No card drill-down​

The cards in this view do not expand. To investigate which specific config is dragging a group into the breached or at-risk state, use Vault Operations > Vault Data Sync Dashboard.

Auto-refresh​

The dashboard polls GET /api/bucket-groups/dashboard every 30 seconds. A countdown timer and ms response-time badge are displayed alongside the Refresh button.

Workflows​

Morning RPO review​

  1. Open the Group Health tab.
  2. Scan for red (breached) or amber (at risk) cards. Emerald (compliant) cards require no action.
  3. For each red card, note the group name and any unprotected bucket count shown on the card.
  4. Move to Vault Operations > Vault Data Sync Dashboard to identify exactly which buckets in the group are lagging, then use Sync Group Now there to trigger a manual catch-up sync (Preparation Mode only — in Vault Mode the vault agent runs the syncs on its schedule).
  5. Return to Group Health after the jobs complete; the lag bar should drop back inside the RPO target and the badge return to Compliant.

Escalating a persistent RPO breach​

  1. Note the breached group's name and current lagHours (shown below the progress bar).
  2. Move to Vault Operations > Vault Data Sync Dashboard and list every bucket in the group.
  3. Find buckets with failed or partial windows (shown in the bucket row; a bucket with nothing pending shows All synced) and expand them to see the windows.
  4. Use the failed window's time range on Copy Jobs - Live View & History to locate the failed job and open the job detail flyout for the error log.

Checking group health after a vault maintenance window​

  1. After the vault agent comes back online, open this tab and Refresh.
  2. Any groups that breached during the maintenance period will show red cards with a lag bar exceeding 100 %.
  3. In Preparation Mode, trigger manual incremental syncs with Sync Group Now (Vault Operations > Vault Data Sync Dashboard) for the affected groups; in Vault Mode the vault agent catches up on its schedule.
  4. Monitor until all cards return to Compliant before closing the maintenance ticket.

Tips​

  • A group card that flickers between amber and emerald across multiple refresh cycles usually indicates intermittent connectivity between the copy engine and the vault device. Check network stability before concluding it is a data problem.
  • A group with many configs may show breached even if only one config is failing — use Vault Operations > Vault Data Sync Dashboard to find the specific bucket.
  • lagHours is the single best indicator of how stale the vault copy is. The numeric label below the progress bar shows it precisely; the "last sync" phrase above the bar is a human-friendly summary.
  • A card with Unknown status means no successful sync has ever been observed for any config in the group. This usually means the group is newly configured — trigger a first full copy from Full Data Sync Management.
  • If all groups show breached or unknown simultaneously, the most likely cause is a system-wide issue (vault agent offline, network partition, copy engine pool unavailable). Check Agent Fleet Management first.