SQL log chain break: detection and repair
Overview
Transaction log backups must be an unbroken chain until a full; breaks mean cannot restore to point-in-time.
Detection
Backup job warnings, SQL errorlog “BACKUP LOG cannot be performed” due to recovery model changes.
Common causes
Switching to SIMPLE during maintenance and forgetting; rogue SHRINK after bulk load without log backup.
Repair path
Take fresh FULL backup after stabilization; document gap accepted by business.
Prevention
Change control on recovery model; monitoring alert on model drift.
Client comms
Explain data loss window if chain unrecoverable—get written acknowledgment.
Related Articles
EDR deployment checklist for new workstations
## Overview Use this runbook when onboarding a new Windows workstation or re-imaging a device that...
Handling Defender for Business false positives
## Overview False positives waste analyst time and train users to ignore alerts. This article stand...
Application allowlisting with Windows Defender ASR rules
## Overview Attack Surface Reduction (ASR) rules reduce exploit surface by constraining Office macr...