Return
-
Title
How to re-initialize Log Shipping on versions 7.x and 8.x of LiteSpeed -
Description
What are the steps to reinitialize Log Shipping on 7.x and 8.x versions of LiteSpeed? -
Cause
The restore job may fail in the following cases:- The job is disabled.
- Backup folder cannot be found.
- Access to shared backup folder is denied.
- LiteSpeed for SQL Server has been removed from the subscriber server.
- The publisher database has been renamed, or removed, or not accessible.
- The t-log was manually backed up on the Publisher and there were database changes.
- Database is not in the "Stand by" or "No Recovery" state.
- Synchronizing subscribers failed.
-
Resolution
To reinitialize log shipping from the LiteSpeed Console.Right-click the Subscriber database in the Monitoring tab and select Reinitialize.NOTE: When you reinitialize log shipping, the plan status is updated only after usual backup transaction log, copy and restore jobs are completed. You can also re-initialize log shipping using stored procedures (see example below). These steps are documented in the LiteSpeed Configure Log Shipping User Guide. Also, available in the LiteSpeed Help File - press F1 in the LiteSpeed Console.Reinitialize Log Shipping after finding the Log Shipping Plan ID./* this script executes on the publisher: */exec LogShipping_Update_PrimaryDatabase@PlanID = 'c2a43886-5da2-40ef-b03d-693ebf185db6'@PerformBackup = 1/* this script executes on subscribers: */exec LogShipping_Sync_Subscriber@PlanID = 'c2a43886-5da2-40ef-b03d-693ebf185db6'