May 8, 2012 at 12:56 pm
Hi,
What is the quickest way to recover from the problem for a very large data base?
Thanks!!
May 8, 2012 at 2:14 pm
Quickest would likely be to sort out your sync issue. Where are the logs? Do you have any confidence in being able to get back on track without rebuilding? How big is the database?
If you cannot sort it out then you'll need to rebuild. Remove log shipping, then recreate log shipping from a full backup of the primary.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
May 8, 2012 at 2:53 pm
Thanks for your answer!!
I get 14420 and 14421 error messages.
The database is bigger than 1TB.
What do you mean by sort out? Do you mean get it running again?
I would like to get it working again without a rebuild since it takes too
much time, but I'm not sure what other options there are?
May 8, 2012 at 3:46 pm
hedlund_peter (5/8/2012)
Thanks for your answer!!I get 14420 and 14421 error messages.
The database is bigger than 1TB.
What do you mean by sort out? Do you mean get it running again?
I would like to get it working again without a rebuild since it takes too
much time, but I'm not sure what other options there are?
OK, that is a different issue than what I thought. I thought you got out of sequence with your log backups and restores meaning, like a broken log chain, or someone taking a manual log backup and you not being able to get to it...what you are experiencing is a delay in your log backups and restores, i.e. you are not broken, just behind.
Article says it applies to SQL 2000 and 2005 but all info is still relevant for 2008.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply