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.
SQL Safe offers log shipping policies, backup policies, and restore policies to address different needs.
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 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 policies to synchronize, or back up and restore one database to another. By synchronizing databases through this policy, you can save disk space, network bandwidth, and comply with security requirements. Each transaction log backup can be compressed and encrypted.
How do you access the Log Shipping wizard?
You can access the Log Shipping Policy Wizard from the following tabs: Home, Policies, Instances, and Databases. On any of these tabs, click Create Policy and then choose Log Shipping Policy.
To get started with the Log Shipping Policy wizard, follow these steps:
- Name the policy.
- Select the primary database that you want to back up.
- Specify where these transaction log files should be stored.
- Select the secondary database you want to synchronize with the primary.
- Select the notifications you want to receive for this policy.
- Review details.