The General tab of the Log Shipping Policy wizard allows you to specify the basic properties of the log shipping policy.
Why should you specify a name or description?
The wizard requires you to enter a unique name for each policy. Both the name and description will appear in the status messages for your policies. Using a meaningful name and description will allow you to more easily identify problems when they occur. For example, consider specifying a description that will help you later choose the correct backup to restore during a disaster recovery situation.
What options are available for creating a log shipping policy?
When you create a log shipping policy, you can choose between the two following actions:
- Create Backup and Restore Jobs using the SQL Server Agent.
- Create Backup and Restore Jobs using the SQL Safe Backup Agent.
Note that SQL Server Express does not support the SQL Server Agent. Use the second option if you add any instance with SQL Server Express in your policy. This option allows the SQL Safe Backup Agent (second option) to create your log shipping policy job.
How does SQL Safe determine that a log shipping policy is okay?
SQL Safe determines that the policy is okay by looking at the following statuses:
- Whether the transaction log backup on the primary database has completed on schedule.
- Whether the transaction log restore on the secondary database has completed without warnings or errors.
- Whether the data on the secondary database is stable.
How do you control when a log shipping policy is compliant?
You can control how SQL Safe determines a missed backup by changing these options:
- Select a time limit for the log backup to occur. This is the leeway time allowed for the log backup to occur. If the log backup occurs within this period from the scheduled time, the policy is still compliant.
- Select an age limit for the secondary's data. This is the tolerance level for how old the data in the secondary database can be.
After defining your setting in this tab, click Next to select the primary database.