← cigardev.xyz

Rubrik Triage

Last updated: September 11, 2026 at 9:13 AM ET
🔴 7 Critical ⚠️ 3 Warnings 🙋 2 Replies 👀 5 Watching

Critical

⚠️ Rubrik: Periodic node task failures – Milwaukee CRITICAL
Cluster: htv001mlwrbk001 → Milwaukee
Object: Nodes RVMHM191S004070/004072/004136/004373
Recurred again 9/11: task failures on 004072 and 004136, plus new NtpClockOffsetPeers health-monitor Critical. Continuing since 7/16 (~8 weeks).
Rubrik: Network interface down - Fort Myers CRITICAL
Cluster: hts001fmtrbk001 → Fort Myers
Object: Nodes RVMHM187S009415, 009048, 009418
Recurred again 9/11 (same 3 nodes): network interface rketh3 down. Continuing since 7/10 (9+ weeks).
Rubrik: Widespread backup failures - Louisville CRITICAL
Cluster: hts001lourbk001 → Louisville
Object: 25+ objects, new PBQLIKEM110A/B volumes today
19+ Critical backup failures overnight (04:04-04:25 AM), fully matched by Daily Event Report — no coverage gap. Over 11 weeks running, no support case open.
⚠️ Rubrik: Backup failure – Boston (WCVB-TVM1) CRITICAL
Cluster: htv001bosrbk001 → Boston (WCVB)
Object: 4099 Station Max/Prism Fileset
Recurred again 9/11 — hostname resolution + snapshot creation failed. Ongoing since 8/19.
⚠️ Rubrik: Snapshot failures – Kansas City CRITICAL
Cluster: htv001kscrbk001 → Kansas City (KMBC)
Object: KMBC-SIG-AGENT, KMBC-SC1 (Florical) Smart Central
Recurred again 9/11 via genuine snapshot-failed Critical alerts, confirmed by Daily Event Report. Same host 10.141.54.160.

Warnings

⚠️ Rubrik: Backup/upload failures – Westbrook (multiple objects) WARNING
Cluster: htv001wbkrbk001 → Westbrook, ME (WMTW)
Object: 005351/005414/005439 node tasks, WMTW-WEB, composite list
Recurred again 9/11: node task failure on 005351/005439, archive upload failure on WMTW-WEB. Corroborates P1 case #01308275.
Rubrik: RBS unreachable – Jackson WARNING
Cluster: htv001jksrbk001 → Jackson
Object: 10.158.14.101, 10.158.36.114
Both hosts unreachable again 9/11. Unresolved 10+ weeks running.
⚠️ Rubrik: Storage over 90% full – Boston WARNING
Cluster: htv001bosrbk001 → Boston
Storage still over 90% full, recurred again 9/11 (05:13 AM EDT).
Rubrik: Remote cluster unreachable – Louisville to Dallas WARNING
Cluster: hts001lourbk001 → Louisville
Object: Remote cluster hts001dalrbk002 (Dallas)
Recurred again 9/11 (06:28 UTC).

Support Cases

🔴 Rubrik: P1 Case #01308275 – htv001wbkrbk001, Westbrook (Node is Bad) CRITICAL Corroborated Reply needed
Cluster: htv001wbkrbk001 → Westbrook, ME (WMTW)
Object: Node RVMHM188S005439
No new update from Rubrik Support since 9/9 (status: Waiting for Customer Input — support tunnel + maintenance confirmation requested). Cluster still shows active Critical alerts today, corroborating the case.

Needs Reply

Rubrik Support case #01291904 (P3) – node removal, hts001nycrbkclus Reply needed
Cluster: hts001nycrbkclus
Assistance requested: node removal from CDM cluster for relocation to new site. Latest update 9/9; P3 so not tracked in the state machine, but appears to need Scott's input.

Watching

Rubrik: Archival connection failure – GCP (hts001albrbk001) CRITICAL
Cluster: hts001albrbk001
Failed to connect to archival location 08:21 EDT; self-resolved 5 min later. Day 1 — watching for recurrence.
Rubrik: Backup failure – Oklahoma City (KOCO-ABX2, Florical Folder) CRITICAL
Cluster: htv001okcrbk001 → Oklahoma City (KOCO)
Creating snapshot failed 05:11 CDT — could not reach host. Day 1 — watching.
Rubrik: Backup failure – Omaha (KETV-CERENG-02) CRITICAL
Cluster: htv001omarbk001 → Omaha (KETV)
Creating snapshot failed 05:11 CDT. Day 1 — watching.
Rubrik: MSSQL log backup failure – Milwaukee (WISN-FCDB1 fsiconfig) CRITICAL
Cluster: htv001mlwrbk001 → Milwaukee (WISN)
Creating MSSQL log failed 04:59 UTC — Rubrik agent internal error. Day 1 — watching.
Rubrik: File retrieval errors – fdbdr-rbkcc-001 (APP30_cfs_PRD) WARNING
Cluster: fdbdr-rbkcc-001
1 error retrieving data during backup, 09:21 UTC. Day 1 — watching.

Things 3 Changes

Refreshed 10 active to-dos in Things 3 and Kando
No creates or closes today — all 10 tracked issues recurred and were updated in place. 5 new issues are Day-1 watching (no to-do yet). Note: 2 Kando cards (Case #01308275, Boston storage) sit in the "Done" column — left untouched per the never-move rule, but both are still active in Things/tracking, so worth a manual check.