How to initiate log shipping again when it is not synchronized?

edit

Check the causes of the unsynchronized state: Before attempting to do anything, it is crucial to identify the causes of the log shipping not being synchronized. Some of the common reasons could be network issues, a failure of the primary or secondary server, or database corruption, among others.

Set Up a Baseline: Setting up a baseline involves backing up the primary database, copying the backup file to the secondary server, and restoring it with "NO-RECOVERY" option. This process sets a starting point for the log shipping process.

Configure and Enable Log Shipping: After setting up the baseline, log in to the primary server and configure log shipping again. Use the original settings and ensure that you set the copy and restore jobs up to the point in time where the log shipping was last synchronized.

Restore the Last Backup: Once the jobs have been created, it is necessary to restore the last backup taken on the primary server to the secondary server using the "NO RECOVERY" option.

Monitor the Process: With the log shipping process initiated, continuously monitor the log shipping status to ensure that the synchronization is taking place.

Troubleshoot Issues: Monitor the logs to identify any errors that could occur during the log shipping process. If any errors are identified, troubleshoot and resolve them before they become severe.

Ensure That Security Settings Are Correct: Double-check the security settings on the backup file and secondary server to ensure that they are accurate.

Reconfigure Security Settings: If the security settings do not match the log shipping configuration settings, then configure them accordingly.

Repeat: If the synchronization is successful, continue with the log shipping process. If not, repeat the process until synchronization is achieved.