Log shipping recreate

shaikh shoaib 171 Reputation points

Due to LSN number mismatch, log shipping is failing for one Database. Since it has a long list trn backups, wondering if this would be easy to remove the secondary node from log shipping and add it back again.

What is the correct process?

I can remove the secondary server from shipping in primary server Database - transaction log shipping and re-add it?

I this a seamless process / or do I need to do anything on the shipping server?


SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,114 questions
{count} votes

Accepted answer
  1. CathyJi-MSFT 21,111 Reputation points Microsoft Vendor

    Hi @shaikh shoaib ,

    Yes, you can do that follow below steps.

    1. Remove a Secondary Database a. On the primary server, execute sp_delete_log_shipping_primary_secondary to delete the information about the secondary database from the primary server. b. On the secondary server, execute sp_delete_log_shipping_secondary_database to delete the secondary database. c. On the secondary server, disable the copy and restore jobs. For more information, see Disable or Enable a Job.

    2.Disable the log shipping jobs on primary server.

    3.Back up the database on primary server.

    4.Restore the database with the backup you just created and with no recovery on secondary server.

    5.Re-enable the log shipping jobs on both servers.

    Refer to the MS document Remove a Secondary Database from a Log Shipping Configuration (SQL Server).

    If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar thread.

0 additional answers

Sort by: Most helpful