Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I've set up log shipping from Server A to Server B. I then set it up from B to A when B was the primary.

I've reverted back to A being primary and disabled the backup, copy and restore jobs associated with B to A shipping. However, I have a failure of the LSAlert job on both A and B.

Is there a way to suppress these error or must I remove Log Shipping from B to A while A is primary?

My goal is to leave the log shipping configuration in place for DR, but have it not raise errors stating that databases have not been sync'd.

Thanks

share|improve this question
add comment

1 Answer

up vote 1 down vote accepted

This normally occurs when the log-shipping is not removed cleanly. To remove the orphan entries you have to delete them from msdb logshipping tables.

On Primary :
delete from msdb..log_shipping_monitor_secondary
where secondary_database = '' -- secondary db name goes here 
delete from dbo.log_shipping_secondary
where primary_database='' -- primary db name goes here 

On Secondary:

delete from msdb..log_shipping_monitor_primary
where primary_database='' -- primary db name goes here 

delete from dbo.log_shipping_primary_secondaries
where secondary_database='' -- secondary db name goes here 
share|improve this answer
    
My goal is to leave the log shipping configuration in place for DR, but have it not raise errors stating that databases have not been sync'd. –  Sam Apr 4 '13 at 20:07
    
Use the above sql to check the logshipping tables where there are orphan entries e.g. B is primary and A is seconday --> since you have removed the logshipping, but still the logshipping tables have entries in it as they are not properly cleaned up. –  Kin Apr 4 '13 at 20:30
    
I have not removed log shipping, nor do I want to. I have only disabled jobs. –  Sam Apr 4 '13 at 20:32
    
If that is the case, then the logshipping alert will fail. There is no way unless you disable the alert job. Also, can you check the tables that I mentioned to see if it does not have any orphan entires –  Kin Apr 4 '13 at 20:54
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.