zoom_in Click to enlarge

SQL Server Log Shipping

▲ ▼

description SQL Server Log Shipping Overview

SQL Server log shipping is a disaster-recovery feature that repeatedly backs up a primary database's transaction log, copies the backup files to one or more secondary servers, and restores them there. The secondary database can remain unavailable or be placed in read-only standby mode between restores. Recovery requires a controlled failover and may lose transactions created after the most recent copied and restored log backup, so it is not an automatic high-availability mechanism.

help SQL Server Log Shipping FAQ

What is SQL Server log shipping?

Log shipping repeatedly backs up a SQL Server database's transaction log, copies the backup to one or more secondary servers, and restores it there. Microsoft SQL Server has supported this disaster-recovery feature for many years.

Is the secondary database in log shipping writable?

The secondary database is normally left in a restoring state or placed in standby, which can allow read-only access between restores. It is not an active writable replica for ordinary application traffic.

How quickly does SQL Server log shipping copy changes?

The recovery-point gap depends on the backup, copy, and restore schedules. A setup running every few minutes can reduce the gap, but it remains asynchronous and can lose transactions since the last successful log backup.

swap_horiz

Looking for SQL Server Log Shipping alternatives? Compare top competitors ranked & scored

arrow_forward