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-07-04 07:35
Critical5
Action0
Watch0
Stable0
Open actions23
Runtime events2757
Telemetry gaps0
Growth0.0 GB
Operational impact 0 / 100 High exposure ยท evidence coverage 100%
Recovery readiness Backup chains, restore confidence and failed maintenance are folded into each server's actions.
20
Capacity protection Low disk, database growth and projected pressure are visible before they become write failures.
0
Service reliability Failed jobs, runtime events, deadlocks, blocking and long-running queries are treated as connected reliability evidence.
2760
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 1

TESTSRV_1.DBNEXIA.COM / Test / SQL Server / Last seen 2026-07-04 07:35
Health0
Pressure100
TrendDeteriorating
DirectionRising risk
Best advice

P1 Backup: Repair backup chain for DOM_BlossomWhisper_FDD3 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, 6 database backup chains crossed the configured risk threshold; 989 log/runtime events were recorded, latest at 2026-07-03 23:47; 1 deadlocks and 0 blocking events appeared; databases grew by 0.0 GB in the selected window.

What is happening

Right now, the error/log stream is active; sessions are waiting on blockers or deadlock-prone paths; restore confidence is degraded.

What happens next

Restore risk will continue to increase until the broken backup chain is repaired and verified. Pressure indicators: 989 projected runtime events in 24 hours, 7 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_BlossomWhisper_FDD3 and validate restore.

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

Trace blockers/deadlocks to statement, index, and transaction order.

Concurrency incidents usually repeat under the same application path until the blocking pattern is removed.
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
6 Backups
0 Disk
0 Jobs
989 Logs
1 Locks
0 Queries
0 Gaps
6 backup 989 log/runtime 1 blocking
Concrete findings 11
Backups DOM_BlossomWhisper_FDD3

FULL missing, LOG missing

Backups DOM_DreamBlossom_D66E

FULL missing, LOG missing

Backups DOM_ForestDream_BD6D

FULL missing, LOG missing

Logs 988 Errors

2026-07-03 23:47 - The specified @name ('MAL_MAINT_MAINT_JOB') already exists.

Logs 1 Timeouts

2026-07-03 23:47 - The specified @name ('MAL_MAINT_MAINT_JOB') already exists.

Deadlocks database unknown

2026-07-03 11:55 - <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-07-03T11:55:15.544Z"><data name="xml_report"><value><deadlock><victim-list><vict...

Growth tempdb

0.0 GB growth (Log ).

Largest DB dbNexia_db

0.8 GB current size.

Largest DB MAL_MAINT_DB

0.8 GB current size.

Resources CPU and memory

CPU 1.0%, memory free 31.3%, users 1, transactions 7.

TempDB Data and log

Data 1.5%, log 23.0%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-07-04 06:26, last failed -. 6 backup risks. 989 runtime events. 1 deadlocks / 0 blocking. 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; remove blocker/deadlock source; triage latest log errors.
CPU / memory free 1.0% / 31.3%
TempDB data / log 1.5% / 23.0%
Growth now / 7d forecast 0.0 GB / 0.1 GB
Runtime / 24h forecast 989 / 989
Backups / disks / jobs 6 / 0 / 0
Blocking / long queries 1 / 0
Telemetry gaps 0
Largest database 0.8 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 1.39 GB
Last OK 2026-07-04 06:26
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 989 events

Errors 988, timeouts 1, login failures 0, CPU warnings 0, memory grants 0.

The specified @name ('MAL_MAINT_MAINT_JOB') already exists.

Meaning

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

Recommended fix

Run or repair the log-backup job for database 'Errors 988, timeouts 1, login failures 0, CPU warnings 0, memory grants 0.'. 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 risks6
DOM_BlossomWhisper_FDD3210/100

FULL missing, LOG missing

Meaning and fix

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

Fix: Run or repair the log-backup job for database 'DOM_BlossomWhisper_FDD3'. 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_DreamBlossom_D66E210/100

FULL missing, LOG missing

Meaning and fix

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

Fix: Run or repair the log-backup job for database 'DOM_DreamBlossom_D66E'. 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_ForestDream_BD6D210/100

FULL missing, LOG missing

Meaning and fix

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

Fix: Run or repair the log-backup job for database 'DOM_ForestDream_BD6D'. 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_ShadowWhisper_67B1210/100

FULL missing, LOG missing

Meaning and fix

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

Fix: Run or repair the log-backup job for database 'DOM_ShadowWhisper_67B1'. 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_ThunderMoon_622B210/100

FULL missing, LOG missing

Meaning and fix

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

Fix: Run or repair the log-backup job for database 'DOM_ThunderMoon_622B'. 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.

dbNexia_db180/100

FULL missing

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.

Storage0 low volumes
StorageNo low volumes

No low free-space volumes detected for this server.

Growth0.0 GB
tempdb12.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 concurrency1 signals
Deadlock2026-07-03 11:55

database unknown; <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-07-03T11:55:15.544Z"><data name="xml_report"><value><deadlock><victim-list><vict...

Meaning and fix

Meaning: SQL Server detected two sessions holding resources in conflicting order and chose one session as the deadlock victim.

Fix: Use the deadlock event details to identify the two statements and objects. Add the missing supporting index or change the transaction order so both code paths touch objects in the same order.

Verify: After the change, the same database/object pair should stop producing deadlock events in the selected lookback window.

Largest databases and job failures0 job failures
dbNexia_db0.8 GB

Current largest database inventory sample.

MAL_MAINT_DB0.8 GB

Current largest database inventory sample.

MAL_MAINT_DB_old0.1 GB

Current largest database inventory sample.

DOM_ForestDream_BD6D0.1 GB

Current largest database inventory sample.

DOM_DreamBlossom_D66E0.1 GB

Current largest database inventory sample.

DOM_ShadowWhisper_67B10.1 GB

Current largest database inventory sample.

DOM_ThunderMoon_622B0.0 GB

Current largest database inventory sample.

tempdb0.0 GB

Current largest database inventory sample.

DOM_BlossomWhisper_FDD30.0 GB

Current largest database inventory sample.

JobsNo failures

No SQL Agent job failures detected in this window.

Critical

SERVER 2

TESTSRV_2.DBNEXIA.COM / Test / SQL Server / Last seen 2026-07-04 07:35
Health0
Pressure100
TrendDeteriorating
DirectionRising risk
Best advice

P1 Backup: Repair backup chain for DOM_DreamStone_5722 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, 6 database backup chains crossed the configured risk threshold; 876 log/runtime events were recorded, latest at 2026-07-03 21:30.

What is happening

Right now, the error/log stream is active; restore confidence is degraded.

What happens next

Restore risk will continue to increase until the broken backup chain is repaired and verified. Pressure indicators: 876 projected runtime events in 24 hours, 6 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 2
P1
Backup

Repair backup chain for DOM_DreamStone_5722 and validate restore.

Current evidence indicates high restore risk; this must be fixed before a real incident.
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
6 Backups
0 Disk
0 Jobs
876 Logs
0 Locks
0 Queries
0 Gaps
6 backup 876 log/runtime
Concrete findings 8
Backups DOM_DreamStone_5722

FULL missing, LOG missing

Backups DOM_ForestEcho_B4A4

FULL missing, LOG missing

Backups DOM_ForestSky_5A7D

FULL missing, LOG missing

Logs 876 Errors

2026-07-03 21:30 - Conversion failed when converting the nvarchar value 'Updated_2414' to data type bit.

Largest DB MAL_MAINT_DB

0.8 GB current size.

Largest DB DOM_ForestSky_5A7D

0.1 GB current size.

Resources CPU and memory

CPU 1.0%, memory free 31.3%, users 1, transactions 7.

TempDB Data and log

Data 35.6%, log 41.0%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-07-04 06:26, last failed -. 6 backup risks. 876 runtime events. CPU 1.0%, memory free 31.3%. TempDB data 35.6%, log 41.0%.

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; triage latest log errors.
CPU / memory free 1.0% / 31.3%
TempDB data / log 35.6% / 41.0%
Growth now / 7d forecast 0.0 GB / 0.0 GB
Runtime / 24h forecast 876 / 876
Backups / disks / jobs 6 / 0 / 0
Blocking / long queries 0 / 0
Telemetry gaps 0
Largest database 0.8 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 1.39 GB
Last OK 2026-07-04 06:26
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 876 events

Errors 876, timeouts 0, login failures 0, CPU warnings 0, memory grants 0.

Conversion failed when converting the nvarchar value 'Updated_2414' to data type bit.

Meaning

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

Recommended fix

Run or repair the log-backup job for database 'Errors 876, timeouts 0, login failures 0, CPU warnings 0, memory grants 0.'. 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 risks6
DOM_DreamStone_5722210/100

FULL missing, LOG missing

Meaning and fix

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

Fix: Run or repair the log-backup job for database 'DOM_DreamStone_5722'. 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_ForestEcho_B4A4210/100

FULL missing, LOG missing

Meaning and fix

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

Fix: Run or repair the log-backup job for database 'DOM_ForestEcho_B4A4'. 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_ForestSky_5A7D210/100

FULL missing, LOG missing

Meaning and fix

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

Fix: Run or repair the log-backup job for database 'DOM_ForestSky_5A7D'. 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_ShadowRiver_9AF6210/100

FULL missing, LOG missing

Meaning and fix

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

Fix: Run or repair the log-backup job for database 'DOM_ShadowRiver_9AF6'. 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_WhisperEcho_929E210/100

FULL missing, LOG missing

Meaning and fix

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

Fix: Run or repair the log-backup job for database 'DOM_WhisperEcho_929E'. 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.

dbNexia_db180/100

FULL missing

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.

Storage0 low volumes
StorageNo low volumes

No low free-space volumes detected for this server.

Growth0.0 GB
GrowthNo rows

No database growth rows detected for this window.

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
MAL_MAINT_DB0.8 GB

Current largest database inventory sample.

DOM_ForestSky_5A7D0.1 GB

Current largest database inventory sample.

DOM_DreamStone_57220.1 GB

Current largest database inventory sample.

MAL_MAINT_DB_old0.1 GB

Current largest database inventory sample.

DOM_ShadowRiver_9AF60.0 GB

Current largest database inventory sample.

DOM_ForestEcho_B4A40.0 GB

Current largest database inventory sample.

DOM_WhisperEcho_929E0.0 GB

Current largest database inventory sample.

tempdb0.0 GB

Current largest database inventory sample.

JobsNo failures

No SQL Agent job failures detected in this window.

Critical

SERVER 3

TESTSRV_3.DBNEXIA.COM / Test / SQL Server / Last seen 2026-07-04 07:35
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, 6 database backup chains crossed the configured risk threshold; 892 log/runtime events were recorded, latest at 2026-07-03 21:30.

What is happening

Right now, the error/log stream is active; restore confidence is degraded.

What happens next

Restore risk will continue to increase until the broken backup chain is repaired and verified. Pressure indicators: 892 projected runtime events in 24 hours, 6 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 2
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.
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
6 Backups
0 Disk
0 Jobs
892 Logs
0 Locks
0 Queries
0 Gaps
6 backup 892 log/runtime
Concrete findings 9
Backups DOM_CrystalStone_911A

FULL missing, LOG missing

Backups DOM_FlameCrystal_07F4

FULL missing, LOG missing

Backups DOM_MoonCrystal_16FD

FULL missing, LOG missing

Logs 891 Errors

2026-07-03 21:30 - Conversion failed when converting the nvarchar value 'Updated_7330' to data type bit.

Logs 1 Timeouts

2026-07-03 21:30 - Conversion failed when converting the nvarchar value 'Updated_7330' to data type bit.

Largest DB MAL_MAINT_DB

0.9 GB current size.

Largest DB DOM_ShadowOcean_4486

0.1 GB current size.

Resources CPU and memory

CPU 1.0%, memory free 31.3%, users 1, transactions 7.

TempDB Data and log

Data 32.3%, log 7.9%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-07-04 06:26, last failed -. 6 backup risks. 892 runtime events. CPU 1.0%, memory free 31.3%. TempDB data 32.3%, log 7.9%.

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; triage latest log errors.
CPU / memory free 1.0% / 31.3%
TempDB data / log 32.3% / 7.9%
Growth now / 7d forecast 0.0 GB / 0.0 GB
Runtime / 24h forecast 892 / 892
Backups / disks / jobs 6 / 0 / 0
Blocking / long queries 0 / 0
Telemetry gaps 0
Largest database 0.9 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 1.45 GB
Last OK 2026-07-04 06:26
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 892 events

Errors 891, timeouts 1, login failures 0, CPU warnings 0, memory grants 0.

Conversion failed when converting the nvarchar value 'Updated_7330' to data type bit.

Meaning

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

Recommended fix

Run or repair the log-backup job for database 'Errors 891, timeouts 1, login failures 0, CPU warnings 0, memory grants 0.'. 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 risks6
DOM_CrystalStone_911A210/100

FULL missing, LOG missing

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_07F4210/100

FULL missing, LOG missing

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_16FD210/100

FULL missing, LOG missing

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_946A210/100

FULL missing, LOG missing

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_4486210/100

FULL missing, LOG missing

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.

dbNexia_db180/100

FULL missing

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.

Storage0 low volumes
StorageNo low volumes

No low free-space volumes detected for this server.

Growth0.0 GB
GrowthNo rows

No database growth rows detected for this window.

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
MAL_MAINT_DB0.9 GB

Current largest database inventory sample.

DOM_ShadowOcean_44860.1 GB

Current largest database inventory sample.

MAL_MAINT_DB_old0.1 GB

Current largest database inventory sample.

DOM_CrystalStone_911A0.1 GB

Current largest database inventory sample.

DOM_ShadowMoon_946A0.0 GB

Current largest database inventory sample.

DOM_MoonCrystal_16FD0.0 GB

Current largest database inventory sample.

DOM_FlameCrystal_07F40.0 GB

Current largest database inventory sample.

tempdb0.0 GB

Current largest database inventory sample.

JobsNo failures

No SQL Agent job failures detected in this window.

Critical

SERVER 5

TESTSRV_5.DBNEXIA.COM / Test / SQL Server / Last seen 2026-07-04 07:35
Health76
Pressure36
TrendStable
DirectionNo negative trend
Best advice

P1 Backup: Repair backup chain for dbNexia_db and validate restore. This is first because current evidence indicates high restore risk; this must be fixed before a real incident. Pattern: SQL Agent jobs are failing repeatedly inside the selected review window.

Dashboard Report
What happened

In the selected window, 1 database backup chains crossed the configured risk threshold; 2 SQL Agent failures were captured.

What is happening

Right now, maintenance or business jobs need human follow-up; restore confidence is degraded.

What happens next

Restore risk will continue to increase until the broken backup chain is repaired and verified. Pressure indicators: 3 action signals. The likely outcome is operational impact or missed recovery objectives unless the first action is handled immediately.

Actions to break the trend 2
P1
Backup

Repair backup chain for dbNexia_db and validate restore.

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

Fix and rerun failed job: dbNexia_Process_Logs.

Failed jobs leave maintenance, imports, or business data in an unknown state.
Trend and signal mix No negative trend
1 Backups
0 Disk
2 Jobs
0 Logs
0 Locks
0 Queries
0 Gaps
1 backup 2 job
Concrete findings 7
Backups dbNexia_db

FULL missing

Jobs dbNexia_Process_Logs

2026-07-04 07:35 - ServerMetrics: Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplicate key in ...

Jobs MAL_MAINT_Process_Logs

2026-07-04 07:10 - ServerMetrics: Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplicate key in ...

Largest DB MAL_MAINT_DB

0.6 GB current size.

Largest DB tempdb

0.0 GB current size.

Resources CPU and memory

CPU 1.0%, memory free 31.3%, users 3, transactions 9.

TempDB Data and log

Data 15.3%, log 17.5%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-07-04 06:26, last failed -. 1 backup risks. 2 job failures. CPU 1.0%, memory free 31.3%. TempDB data 15.3%, log 17.5%.

Recommended action Repair the backup chain now and validate restore coverage for the highest-risk databases.
Pattern SQL Agent jobs are failing repeatedly inside the selected review window.
Forecast Restore risk will continue to increase until the broken backup chain is repaired and verified.
Break the trend validate backup and restore path; fix failing SQL Agent jobs.
CPU / memory free 1.0% / 31.3%
TempDB data / log 15.3% / 17.5%
Growth now / 7d forecast 0.0 GB / 0.0 GB
Runtime / 24h forecast 0 / 0
Backups / disks / jobs 1 / 0 / 2
Blocking / long queries 0 / 0
Telemetry gaps 0
Largest database 0.6 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 1.33 GB
Last OK 2026-07-04 06:26
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 0 events

No runtime event sample was loaded for this server.

No latest runtime message captured.

Meaning

database 'No runtime event sample was loaded for this server.' needs a newer log backup in the SQL backup chain.

Recommended fix

Run or repair the log-backup job for database 'No runtime event sample was loaded for this server.'. 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 risks1
dbNexia_db180/100

FULL missing

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.

Storage0 low volumes
StorageNo low volumes

No low free-space volumes detected for this server.

Growth0.0 GB
GrowthNo rows

No database growth rows detected for this window.

Queries and concurrency0 signals
Queries and concurrencyNo signals

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

Largest databases and job failures2 job failures
MAL_MAINT_DB0.6 GB

Current largest database inventory sample.

tempdb0.0 GB

Current largest database inventory sample.

dbNexia_Process_Logs2026-07-04 07:35

ServerMetrics: Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplicate key in ...

Meaning and fix

Meaning: job 'dbNexia_Process_Logs' failed because data handled by the failing step violates a table rule or column limit.

Fix: Use the object/column/key named in the error message. Correct the source data, mapping, or target column size before rerunning the job.

Verify: The rerun should process the same batch without constraint, duplicate key, or truncation errors.

MAL_MAINT_Process_Logs2026-07-04 07:10

ServerMetrics: Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplicate key in ...

Meaning and fix

Meaning: job 'MAL_MAINT_Process_Logs' failed because data handled by the failing step violates a table rule or column limit.

Fix: Use the object/column/key named in the error message. Correct the source data, mapping, or target column size before rerunning the job.

Verify: The rerun should process the same batch without constraint, duplicate key, or truncation errors.

Critical

SERVER 4

TESTSRV_4.DBNEXIA.COM / Test / SQL Server / Last seen 2026-07-04 07:35
Health86
Pressure18
TrendStable
DirectionNo negative trend
Best advice

P1 Backup: Repair backup chain for dbNexia_db and validate restore. This is first because current evidence indicates high restore risk; this must be fixed before a real incident. Pattern: No dominant problem pattern in the collected signals.

Dashboard Report
What happened

In the selected window, 1 database backup chains crossed the configured risk threshold.

What is happening

Right now, restore confidence is degraded.

What happens next

Restore risk will continue to increase until the broken backup chain is repaired and verified. Pressure indicators: 1 action signals. The likely outcome is operational impact or missed recovery objectives unless the first action is handled immediately.

Actions to break the trend 1
P1
Backup

Repair backup chain for dbNexia_db and validate restore.

Current evidence indicates high restore risk; this must be fixed before a real incident.
Trend and signal mix No negative trend
1 Backups
0 Disk
0 Jobs
0 Logs
0 Locks
0 Queries
0 Gaps
1 backup
Concrete findings 5
Backups dbNexia_db

FULL missing

Largest DB MAL_MAINT_DB

0.6 GB current size.

Largest DB tempdb

0.0 GB current size.

Resources CPU and memory

CPU 1.0%, memory free 31.3%, users 1, transactions 7.

TempDB Data and log

Data 9.0%, log 12.2%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-07-04 06:26, last failed -. 1 backup risks. CPU 1.0%, memory free 31.3%. TempDB data 9.0%, log 12.2%.

Recommended action Repair the backup chain now and validate restore coverage for the highest-risk databases.
Pattern No dominant problem pattern in the collected signals.
Forecast Restore risk will continue to increase until the broken backup chain is repaired and verified.
Break the trend validate backup and restore path.
CPU / memory free 1.0% / 31.3%
TempDB data / log 9.0% / 12.2%
Growth now / 7d forecast 0.0 GB / 0.0 GB
Runtime / 24h forecast 0 / 0
Backups / disks / jobs 1 / 0 / 0
Blocking / long queries 0 / 0
Telemetry gaps 0
Largest database 0.6 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 1.33 GB
Last OK 2026-07-04 06:26
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 0 events

No runtime event sample was loaded for this server.

No latest runtime message captured.

Meaning

database 'No runtime event sample was loaded for this server.' needs a newer log backup in the SQL backup chain.

Recommended fix

Run or repair the log-backup job for database 'No runtime event sample was loaded for this server.'. 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 risks1
dbNexia_db180/100

FULL missing

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.

Storage0 low volumes
StorageNo low volumes

No low free-space volumes detected for this server.

Growth0.0 GB
GrowthNo rows

No database growth rows detected for this window.

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
MAL_MAINT_DB0.6 GB

Current largest database inventory sample.

tempdb0.0 GB

Current largest database inventory sample.

JobsNo failures

No SQL Agent job failures detected in this window.