When a specific log shipping policy is selected in the tree pane, the content pane displays information describing the status of that policy. Use this view to determine which backup or restore operations initiated by the policy have succeeded or failed.
What actions can you perform?
From the Log Shipping Policies tree
By right-clicking a policy under the Log Shipping Policies node, you can access the following shortcuts:
Action ... | What it does ... |
|---|---|
Create Log Shipping Policy | Opens the Log Shipping Policy wizard, allowing you to create a new policy. |
Edit Policy | Opens the Log Shipping wizard (with all options pre-set to the values used for this operation), allowing you to edit any of the options. |
Delete Policy | Allows you to delete the policy. Although backup operations associated with this policy will no longer be performed, the previous backup files and status messages created by this policy will continue to be stored in the SQL Safe Repository. |
Disable Policy | Allows you to disable of the selected policy. Backup and restore operations associated with this policy will no longer be performed and email notifications configured on these jobs will be turned off. |
Re-Initialize Secondary Database | Allows you to re-initialize any of the secondary databases associated with the selected policy. |
Refresh Policy List | Updates the Log Shipping Policies node with the latest policies and their statuses. |
From the Current Status pane
By clicking the links available in the Current Status pane, you can access the following shortcuts:
Action ... | What it does ... |
|---|---|
| View Policy Settings | Allows you to view a summary of the policy settings. |
Edit Policy | Opens the Log Shipping Policy wizard, allowing you to change your policy settings. |
Disable Policy | Disables the selected policy. Once a policy is disabled, it will no longer ship transaction logs to the secondary databases and it will no longer send email notifications configured for the respective jobs. |
Start Log Backups | Performs a transaction log backup of the primary database that belongs to this policy by running the corresponding job. This action applies your previously defined policy settings. |
Start Log Restores | Performs a transaction log restore on the secondary databases that belongs to this policy by running the corresponding job. This action applies your previously defined policy settings. |
What does the Current Status mean?
The Current Status displays the most recent, combined status of the backup and restore operations performed by this policy. When there are multiple operation statuses, the policy status reflects the most critical operation status. When all backups and restores have been completed successfully according to the policy schedule, a green okay icon is displayed.
What is the Last Operation Status?
The Last Operation Status shows an overview of the most recent backup, restore, or log shipping operations that occurred across your enterprise. Use this view to quickly determine whether your servers are in compliance with your corporate policies. The operation status is limited to the operations performed by this policy.
What are the Operations Details?
The Operation Details graphic provides the following status details for the primary and secondary databases that belong to the selected policy:
Detail | Description |
|---|---|
Icons | Indicate whether primary and secondary databases remain compliant with the backup and restore schedules defined by the policy. When compliant, the database icons are marked with a green check and the arrow icons pointing from database to database are green. |
State | Indicates whether the database is online or off-line, as well as whether the database is read-only. |
Last Backup | Displays the date and time when the last successful backup was performed. This detail displays for the primary database only. |
Last Restore | Displays the date and time when the last successful restore was performed. This detail displays for each secondary database. |
Latency | Latency measures the amount of time that has elapsed since the last successful restore operation. |
Threshold (primary database) | Indicates how much time can elapse before a scheduled backup is considered missed. When a backup is missed, the policy status is non-compliant. You can change the threshold setting by editing your log shipping policy. |
Threshold (secondary database) | Indicates how much time can elapse after the last successful restore operation before the database is considered stale. When the database becomes stale, the policy status is non-compliant. You can change the threshold setting by editing your log shipping policy. |
Schedule | Displays how often backups are performed on the primary database and how often restores are performed on the secondary databases. |
How do you refresh the Operation Details?
If a recent operation does not appear in the status view, you can refresh the status of this pane by clicking the Refresh icon in the pane title bar.