Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sunsanvin
Master Smack Fu Yak Hacker
1274 Posts |
 Posted - 2009-02-17 : 02:36:54
|
| Dear All,i've faced one interview question, as i'm not that much into logshipping, i failed to answer.there are two servers. one is primary and the other is secondary. primary is production. logshipping configured and working fine.suddnely after some days, the sync between the servers is not there. what is the immediate action?the reason for posting here insted of yak korral is so many people may face the similar question.ArnavEven you learn 1%, Learn it with 100% confidence. |
|
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2009-02-17 : 08:24:11
|
| Guess that depends on what "not there" means. First thing I'd do is check the backup log job and the copy job which copies the job from the primary to secondary and after that check the restore job which restores the log on the secondary. If there are no errors there then I'd start looking in msdb at the log shipping tables (i forget their names now) and see if I could determine the error from there. That's a good question. In general you get these types of questions so that an interviewer can assess your familiarity with the technical stuff and also to get a glimpse of how you work through problems that come up.Mike"oh, that monkey is going to pay" |
 |
|
|
sunsanvin
Master Smack Fu Yak Hacker
1274 Posts |
Posted - 2009-02-17 : 23:46:53
|
| Thank you mfemenelArnavEven you learn 1%, Learn it with 100% confidence. |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-02-17 : 23:49:17
|
| Logshipping - Make sure log are shipped correctly and frequently. |
|
|
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2009-02-18 : 03:31:41
|
| >> What is the immediate action?It depends if you want to get the log shipping back up again really fast or if you want to investigate what happened. Usually what happens to me when log shipping has failed is that someone (or something) has broken the log chain by doing a manual log backup. You'll usually get an error message saying "log too late" or something like that, indicating that the log backup LSNs are not corresponding with what you have restored earlier. The only solution to this is to obtain the missing log backup files and restore those first or do a full backup of the primary database and restore it on the secondary.All other problems I have faced are merely issues regarding copying the log files to the right location or the job stopping or something.- Lumbago |
|
|
|
|
|
|
logshipping interview question