SQL Server 2005 Standard Edition, SQL Server 2005 Workgroup Edition, or SQL Server 2005 Enterprise Edition must be installed on all server instances involved in log shipping. Log shipping has the following requirements: The primary database must use the full or bulk-logged recovery model switching the database to simple recovery will cause log shipping to stop functioning.
All administration of the log shipping configuration through SQL Server Management Studio is performed from the primary database. The primary database is the database on the primary server that you want to back up to another server. The primary server in a log shipping configuration is the instance of the SQL Server database engine that is your production server.
Restore the log backup on the secondary server instance. Copy the transaction log file to the secondary server instance.ģ. Back up the transaction log at the primary server instance.Ģ. Log shipping consists of three operations:ġ.
An optional third server, known as the monitor server, records the history and status of backup and restore operations and optionally raises alerts if these operations fail to occur as scheduled. At the secondary server, these transaction log backups are restored to the secondary database, keeping it closely synchronized with the primary database. Log shipping allows you to automatically send transaction log backups from one database (known as the primary database) to a secondary database on another server (known as the secondary server).
0 kommentar(er)
