Re-Seeding a Broken Log Shipping Secondary (Without Touching the Primary)
A SQL Server upgrade left a log shipping secondary unable to accept transaction logs. Re-seeding it without touching the primary or its mirror is straightforward in principle — drop, restore full + diff + log with NORECOVERY, hand back to the job — but three undocumented traps will stop you along the way. Here's what they are and how to get past them.
2026-10-14
748 reads

