Log shipping policies allow you to ship transaction logs between multiple SQL Server instances in your enterprise, on a scheduled basis. These instances can reside on one or more physical servers.

What is a log shipping policy?

A log shipping policy consists of primary and secondary databases you want to synchronize, a set of transaction log backup and restore operations to be performed on those databases, and a set of schedules according to which these operations will be performed. You can also choose to mirror the backup files, storing copies of the transaction logs in multiple secured locations. You can then monitor the policy status, all from a single point of contact in the Management Console.

How do you log shipping policies help you?

Log shipping policies allow you to implement a disaster recovery strategy for your entire SQL Server environment. You can use log shipping polices to synchronize, or back up and restore, one database to another. Using a log shipping policy to synchronize databases also helps you save disk space and network bandwidth, and comply with security requirements, because each transaction log backup can be compressed and encrypted.

To create log shipping policies, see create a log shipping policy.

To view the status of your log shipping policies, see view status of all log shipping policies or view status of a specific log shipping policy.



 |   |  |  |  |