MysteryJimbo (11/25/2013)
MysteryJimbo (11/25/2013)
This is good, as it means once recovered, the log reader will know everything that still needs to replicate.I should have been clearer. You continue to stand a risk of that undistributed transactions in the distribution db be lost if they weren't captured in the latest backup. The number of these (if any) depends on how busy the system was at the time of the corruption.
Yeah that's a big problem. I guess it's better to reset from scratch by generating the snapshot. Let us assume the distribution server is down and we have to delete the orphan publications so that when we reset it up it will not throw any error saying that it cannot connect to the distribution database as the distribution server is down. This makes the situation more complex as a publisher can have only one distribution database. We have to delete the orphan publications and subscriptions by ignoring the database.
A different scenario, let us assume before doing the maintenance work on distribution server , if we have the latest backups of distribution database and msdb database of distribution server. Can we restore these backups on to a new server(same name as previous distributor server) and kick start the jobs? Does this take care of all the undistributed transactions in the distribution db and the pending transactions on the publisher? Can this be done ? Any suggestions ?