Merry Christmas & Happy 2027! Less downtime. More good times. Celebrating 13 years of sorlavit.com
Skip to content
Sorlavit KimIT Support, Network & Infrastructure Services Let’s talk

ปุ่มแปลไทยจะเปิดบทความผ่าน Google Translate เพื่อแปลอัตโนมัติ โดยคงโค้ดและคำสั่งไว้ตามต้นฉบับ

Data Monitoring / SQL Server Availability & Capacity

SQL Server: Backup age by database

One database has no recent backup although the server-wide chart looks healthy. Compare last successful backup time for every required database with its recovery policy.

Compiled for Sorlavit Kim · Published · Updated · 2 min read

Environment and inputs: SQL Server operational monitoring; availability groups, SQL Agent and host-level metrics depend on edition, service and deployment.

Failure scenario

One database has no recent backup although the server-wide chart looks healthy. Confirm the cause before choosing a fix.

Evidence to collect

Compare last successful backup time for every required database with its recovery policy. Record the time, affected scope and a healthy comparison interval.

Fix the confirmed cause

Alert by database and backup type, accounting for approved exclusions explicitly. Write the expected result first. Change one relevant setting at a time.

Check the result and hand over

Repeat the check for backup age by database using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.

Scope and precautions

Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.

Share this article

Back to all articles