You can use log shipping to send transaction logs from one database (the primary database) to another (the secondary database) on a constant basis. Continually backing up the transaction logs from a primary database and then copying and restoring them to a secondary database keeps the secondary database nearly synchronized with the primary database. The destination server acts as a backup server and provides a way to reallocate query processing from the primary server to one or more read-only secondary servers. Log shipping can be used with databases using the full or bulk-logged recovery models.
For information about which editions of SQL Server support log shipping, see Features Supported by the Editions of SQL Server 2008.
Introduces log shipping concepts and provides an example of a typical log shipping configuration.
Describes the steps involved in configuring a database for log shipping.
Contains information about failing over to a log shipping secondary, changing roles between primary and secondary servers, using secondary servers for query processing, removing log shipping, using log shipping as part of a recovery plan, log shipping tables and stored procedures, and monitoring log shipping.
Describes the server instance used to monitor log shipping activity and keep log shipping history.