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
