liveBook · Manning

Log shipping

As explained in 100 SQL Server Mistakes and How to Avoid Them

Log shipping is a SQL Server disaster-recovery technology that automatically backs up transaction logs, copies them to another server, and restores them to a secondary database.

Log shipping is a SQL Server disaster-recovery technique: transaction logs are backed up, copied to a secondary server, and restored to a secondary database. The database must use the FULL recovery model. section 13.4

Mistake: treating log shipping as a general high-availability replacement.

  • The secondary database cannot come online before failover, so log shipping cannot provide read scaling or offload administrative work. section 13.4
  • After failover, applications must be repointed to the secondary instance, and returning operations in the opposite direction requires reconfiguring log shipping. section 13.4

Delayed recovery window

Apply transaction logs less frequently at the secondary database to create a delay that can help undo an accidental user action before it reaches the secondary. section 13.4

How 100 SQL Server Mistakes and How to Avoid Them covers it

How deep it goes
Defines the backup-copy-restore flow and operational limits, but stops short of implementation commands.
Examples
Uses delayed log application to create a recovery window for accidental user actions.
What it assumes
Requires understanding that participating databases use the FULL recovery model.
What you can do after
Operate log shipping for DR and adjust log-restore frequency to preserve a delayed recovery window.
How it connects
Contrasts log shipping with availability groups, failover clustering, replication, and the FULL recovery model.

This explainer was generated by Manning's knowledge graph from the text of 100 SQL Server Mistakes and How to Avoid Them. The section links point to the parts of the book it draws on.