Action Center

One queue for operational work

Prioritized actions from connectivity, backups, storage, jobs, runtime signals, concurrency and telemetry gaps.

2026-10-17 17:13 24h lookback
Critical11
High20
Watch0
Due now/today31
Affected servers5
Total servers5
Severity shape31 open
Critical
11
High
20
Watch
0
Work categoriestop drivers
Backup
16
Storage
10
Runtime
5
Immediacy31 due now/today
31 immediate 0 planned
Owner loadassignment view
DBA
26
DBA / App owner
5
SLA bucketsplanning pressure
Today
31
Source pageswhere to investigate
Backup Readiness 16 Forecast 10 AI Incidents 5
Priority queue31 open signals
High955
DOM_DreamStone_5722 backup chain needs attention Backup

FULL 20d ago, LOG 475h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_DreamStone_5722 backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High955
DOM_ForestEcho_B4A4 backup chain needs attention Backup

FULL 20d ago, LOG 475h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ForestEcho_B4A4 backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High955
DOM_ForestSky_5A7D backup chain needs attention Backup

FULL 20d ago, LOG 475h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ForestSky_5A7D backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High955
DOM_ShadowRiver_9AF6 backup chain needs attention Backup

FULL 20d ago, LOG 475h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ShadowRiver_9AF6 backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High955
DOM_WhisperEcho_929E backup chain needs attention Backup

FULL 20d ago, LOG 475h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

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

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High955
DOM_CrystalStone_911A backup chain needs attention Backup

FULL 20d ago, LOG 475h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_CrystalStone_911A backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
High955
DOM_FlameCrystal_07F4 backup chain needs attention Backup

FULL 20d ago, LOG 475h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_FlameCrystal_07F4 backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
High955
DOM_MoonCrystal_16FD backup chain needs attention Backup

FULL 20d ago, LOG 475h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_MoonCrystal_16FD backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
High955
DOM_ShadowMoon_946A backup chain needs attention Backup

FULL 20d ago, LOG 475h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ShadowMoon_946A backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
High955
DOM_ShadowOcean_4486 backup chain needs attention Backup

FULL 20d ago, LOG 475h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ShadowOcean_4486 backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
Critical480
DBAChaos backup chain needs attention Backup

FULL 20d ago. Full: 2026-09-27 02:00, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'DBAChaos backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DBAChaos backup chain needs attention'. 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.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
Critical480
dbNexia_db backup chain needs attention Backup

FULL 20d ago. Full: 2026-09-27 02:00, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'dbNexia_db backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'dbNexia_db backup chain needs attention'. 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.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
Critical480
DBAChaos backup chain needs attention Backup

FULL 20d ago. Full: 2026-09-27 02:00, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'DBAChaos backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DBAChaos backup chain needs attention'. 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.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
Critical480
dbNexia_db backup chain needs attention Backup

FULL 20d ago. Full: 2026-09-27 02:00, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'dbNexia_db backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'dbNexia_db backup chain needs attention'. 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.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
Critical480
DBAChaos backup chain needs attention Backup

FULL 20d ago. Full: 2026-09-27 02:00, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'DBAChaos backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DBAChaos backup chain needs attention'. 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.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_5.DBNEXIA.COM Backup Readiness
Critical480
dbNexia_db backup chain needs attention Backup

FULL 20d ago. Full: 2026-09-27 02:00, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'dbNexia_db backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'dbNexia_db backup chain needs attention'. 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.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_5.DBNEXIA.COM Backup Readiness
Critical90
Error pulse detected Runtime

Errors 2722, timeouts 40, login failures 1, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
Meaning

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'Error pulse detected'. 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.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_1.DBNEXIA.COM AI Incidents
Critical90
Error pulse detected Runtime

Errors 2596, timeouts 36, login failures 1, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
Meaning

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'Error pulse detected'. 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.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_2.DBNEXIA.COM AI Incidents
Critical90
Error pulse detected Runtime

Errors 2602, timeouts 51, login failures 4, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
Meaning

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'Error pulse detected'. 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.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_3.DBNEXIA.COM AI Incidents
Critical90
Error pulse detected Runtime

Errors 42, timeouts 41, login failures 0, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
Meaning

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'Error pulse detected'. 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.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_4.DBNEXIA.COM AI Incidents
Critical90
Error pulse detected Runtime

Errors 66, timeouts 55, login failures 1, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
Meaning

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'Error pulse detected'. 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.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_5.DBNEXIA.COM AI Incidents
High78
ANNAT 1 is low on free space Storage

11.5 GB free (28.8%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_1.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

11.5 GB free (28.8%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_1.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

11.5 GB free (28.8%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

11.5 GB free (28.8%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

11.5 GB free (28.8%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

11.5 GB free (28.8%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

11.5 GB free (28.8%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_4.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

11.5 GB free (28.8%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_4.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

11.5 GB free (28.8%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_5.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

11.5 GB free (28.8%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_5.DBNEXIA.COM Forecast