Server Overview

Server operations cockpit

Pick a server and read the current story: what happened, what is happening, what happens next, and exactly what to do first.

Critical 2026-10-14 15:15
Critical3
Action3
Watch0
Stable0
Open actions25
Runtime events8319
Telemetry gaps0
Growth0.1 GB
Operational impact 0 / 100 High exposure ยท evidence coverage 83%
Recovery readiness Backup chains, restore confidence and failed maintenance are folded into each server's actions.
16
Capacity protection Low disk, database growth and projected pressure are visible before they become write failures.
5
Service reliability Failed jobs, runtime events, deadlocks, blocking and long-running queries are treated as connected reliability evidence.
8323
Data confidence Telemetry gaps are counted as risk so empty panels are not mistaken for healthy systems.
0
Action Center Backup Readiness Data Quality
Critical

SERVER 3

TESTSRV_3.DBNEXIA.COM / Test / SQL Server / Last seen 2026-10-14 15:15
Health0
Pressure100
TrendDeteriorating
DirectionRising risk
Best advice

P1 Backup: Repair backup chain for DOM_CrystalStone_911A and validate restore. This is first because current evidence indicates high restore risk; this must be fixed before a real incident. Pattern: Multiple databases have backup chains without fresh evidence.

Dashboard Report
What happened

In the selected window, 7 database backup chains crossed the configured risk threshold; 1 volumes dropped below free-space policy; 2660 log/runtime events were recorded, latest at 2026-10-14 15:03; databases grew by 0.0 GB in the selected window.

What is happening

Right now, the error/log stream is active; storage headroom is below policy; restore confidence is degraded.

What happens next

Restore risk will continue to increase until the broken backup chain is repaired and verified. Pressure indicators: 2,660 projected runtime events in 24 hours, 8 action signals, 1 watch signals. The likely outcome is operational impact or missed recovery objectives unless the first action is handled immediately.

Actions to break the trend 3
P1
Backup

Repair backup chain for DOM_CrystalStone_911A and validate restore.

Current evidence indicates high restore risk; this must be fixed before a real incident.
P2
Storage

Plan capacity cleanup or extension for volumes below policy.

The trend is not yet critical, but continued growth will reduce the time available for a controlled fix.
P1
Logs

Group latest log errors by message and correlate with jobs, releases, and login sources.

The page sees a repeated symptom; grouping tells whether this is one noisy source or a wider server problem.
Trend and signal mix Rising risk
7 Backups
1 Disk
0 Jobs
2660 Logs
0 Locks
0 Queries
0 Gaps
7 backup 1 disk 2660 log/runtime
Concrete findings 12
Backups DOM_CrystalStone_911A

FULL 17d ago, LOG 401h ago

Backups DOM_FlameCrystal_07F4

FULL 17d ago, LOG 401h ago

Backups DOM_MoonCrystal_16FD

FULL 17d ago, LOG 401h ago

Disk ANNAT 1

12.9 GB free (32.2%) of 40.0 GB.

Logs 2,617 Errors

2026-10-14 15:03 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Logs 41 Timeouts

2026-10-14 15:03 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Logs 1 Login failures

2026-10-14 15:03 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Logs 1 Memory grants

2026-10-14 15:03 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Growth dbNexia_db

0.0 GB growth (Log ).

Largest DB DOM_ShadowOcean_4486

0.5 GB current size.

Largest DB DOM_ShadowMoon_946A

0.4 GB current size.

Resources CPU and memory

CPU 11.0%, memory free 39.1%, users 1, transactions 7.

Metrics and evidence Signals

Last OK 2026-10-14 15:15, last failed -. 7 backup risks. Worst disk ANNAT 1 12.9 GB (32.2%). 2660 runtime events. 0.0 GB growth.

Recommended action Repair the backup chain now and validate restore coverage for the highest-risk databases.
Pattern Multiple databases have backup chains without fresh evidence.
Forecast Restore risk will continue to increase until the broken backup chain is repaired and verified.
Break the trend validate backup and restore path; recover or extend disk capacity; triage latest log errors.
CPU / memory free 11.0% / 39.1%
TempDB data / log 2.2% / 7.4%
Growth now / 7d forecast 0.0 GB / 0.1 GB
Runtime / 24h forecast 2660 / 2660
Backups / disks / jobs 7 / 1 / 0
Blocking / long queries 0 / 0
Telemetry gaps 0
Largest database 0.5 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 4.14 GB
Last OK 2026-10-14 15:15
Last failed -
Data quality 100%
Source confidence 0 gaps
AuditLog Available

dbNexia_db.dbo.AuditLog

DbSizes Available

dbNexia_db.dbo.dbsizes

EventLog Available

dbNexia_db.dbo.EventLog

LiveRequests Available

VIEW SERVER STATE permission

MsdbAgent Available

msdb SQL Agent history

MsdbBackup Available

msdb.dbo.backupset

ServerMetrics Available

dbNexia_db.dbo.ServerMetrics

TempDb Available

VIEW SERVER STATE permission

VolumeStats Available

VIEW SERVER STATE permission

Runtime 2660 events

Errors 2,617, timeouts 41, login failures 1, CPU warnings 0, memory grants 1.

(@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Meaning

database 'Errors 2,617, timeouts 41, login failures 1, CPU warnings 0, memory grants 1.' needs a newer log backup in the SQL backup chain.

Recommended fix

Run or repair the log-backup job for database 'Errors 2,617, timeouts 41, login failures 1, CPU warnings 0, memory grants 1.'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Backup risks7
DOM_CrystalStone_911A809/100

FULL 17d ago, LOG 401h ago

Meaning and fix

Meaning: database 'DOM_CrystalStone_911A' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_CrystalStone_911A'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DOM_FlameCrystal_07F4809/100

FULL 17d ago, LOG 401h ago

Meaning and fix

Meaning: database 'DOM_FlameCrystal_07F4' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_FlameCrystal_07F4'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DOM_MoonCrystal_16FD809/100

FULL 17d ago, LOG 401h ago

Meaning and fix

Meaning: database 'DOM_MoonCrystal_16FD' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_MoonCrystal_16FD'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DOM_ShadowMoon_946A809/100

FULL 17d ago, LOG 401h ago

Meaning and fix

Meaning: database 'DOM_ShadowMoon_946A' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_ShadowMoon_946A'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DOM_ShadowOcean_4486809/100

FULL 17d ago, LOG 401h ago

Meaning and fix

Meaning: database 'DOM_ShadowOcean_4486' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_ShadowOcean_4486'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DBAChaos408/100

FULL 17d ago

Meaning and fix

Meaning: database 'DBAChaos' is outside backup freshness policy.

Fix: Run or repair the full-backup job for database 'DBAChaos'. Verify target path, SQL Server service-account permissions, retention cleanup and free space before rerun.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

dbNexia_db408/100

FULL 17d ago

Meaning and fix

Meaning: database 'dbNexia_db' is outside backup freshness policy.

Fix: Run or repair the full-backup job for database 'dbNexia_db'. Verify target path, SQL Server service-account permissions, retention cleanup and free space before rerun.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Storage1 low volumes
ANNAT 112.9 GB free

32.2% free of 40.0 GB on T:\.

Meaning and fix

Meaning: This signal is abnormal, but the row text is not specific enough to name a single root cause with confidence.

Fix: Use the row values already shown here to filter the related report by the same server, database/job/login and the same time window.

Verify: The signal should stop repeating in the next collection window after the underlying job, permission, backup, or workload issue is fixed.

Growth0.0 GB
dbNexia_db18.0 MB

Log growth inside the selected 24h window.

Meaning and fix

Meaning: This signal is abnormal, but the row text is not specific enough to name a single root cause with confidence.

Fix: Use the row values already shown here to filter the related report by the same server, database/job/login and the same time window.

Verify: The signal should stop repeating in the next collection window after the underlying job, permission, backup, or workload issue is fixed.

Queries and concurrency0 signals
Queries and concurrencyNo signals

No long running, blocking, or deadlock signals detected in this window.

Largest databases and job failures0 job failures
DOM_ShadowOcean_44860.5 GB

Current largest database inventory sample.

DOM_ShadowMoon_946A0.4 GB

Current largest database inventory sample.

DOM_FlameCrystal_07F40.4 GB

Current largest database inventory sample.

DOM_CrystalStone_911A0.4 GB

Current largest database inventory sample.

DOM_MoonCrystal_16FD0.4 GB

Current largest database inventory sample.

tempdb0.1 GB

Current largest database inventory sample.

dbNexia_db0.1 GB

Current largest database inventory sample.

DBAChaos0.0 GB

Current largest database inventory sample.

JobsNo failures

No SQL Agent job failures detected in this window.