Friday, March 9, 2012

Removing Log Shipping after disaster

I am trying to get our database back to a "clean" state after a disaster at the weekend. The primary server died - completely - and so the secondary server was promoted to primary. Now, I'd like to remove all traces of log shipping on the server so I can start fresh when our new server arrives imminently.

However, when I try to remove log shipping, SQL tries to connect to the old primary server which of course no longer exists. I can't find anyway to remove the log shipping. What can I do?

Delete the jobs that are doing the backup, copy, and restore. Remove the fileshares. No more log shipping. If this is SQL Server 2000, then just delete the maintenance plan that you used to setup log shipping.|||I've deleted the jobs on what was the secondary server (now the primary). I'm not able to delete the maintenance plans as SQL says I must remove log shipping before deleting the plan. If I try to remove the log shipping, SQL tries to connect to the old machine and fails (as it doesn't exist anymore) .

No comments:

Post a Comment