WHAT'S IN THIS CHAPTER?
- Understanding log shipping
- Taking a look at practical usage scenarios
- Getting to know log-shipping architecture
- Understanding log-shipping deployment
- Role changing within log shipping
- Monitoring and troubleshooting
Log shipping is a low-cost, efficient, and simple SQL Server technique that became available many releases ago, and has been vital to organizations for their business continuity. In log shipping, the database transaction log from one SQL Server is backed up and restored onto a secondary SQL Server, where it is often deployed for high-availability, reporting, and disaster-recovery scenarios. Beginning with SQL Server 2005, log shipping has delivered business continuity, and continues to be one of the high-availability solutions to maintain a warm standby and, with a secondary server, used for failover.
This chapter covers log-shipping architecture and deployment scenarios, and discusses how to configure log shipping and the various scenarios for switching roles between the primary and secondary servers. You also learn how to troubleshoot your log-shipping setup, and how to integrate log shipping with other high-availability solutions.
LOG-SHIPPING DEPLOYMENT SCENARIOS
Log shipping takes advantage of the transaction-log backup and restore functionalities of SQL Server. The two log-shipping SQL Server partners can be located next to each other for high availability, or across a distance for disaster recovery. ...