March 5, 2004 at 8:45 am
Hello,
I thought log shipping was supposed to be so strait forward and easy! It does not appear to be a reliable fail-over or "warm standby" solotion.
After setting up log shipping I have four databases that continue to try an load the first_file_000000000000.trn log, that is created when the plan is first initialized. It happens even though the backup/copy/loads are functioning successfully and according to the plan schedule, and this initial file doesn't even exist in the designated share because it's been deleted according to the log retention schedule. What else should I have expected from Bill and the bunch.....Anyway, here is the error: It's like...tell me something I don't know, like why is this happening!
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4305: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set begins at LSN 33000000022600001, which is too late to apply to the database. An earlier log backup that includes LSN 33000000011800001 can be restored.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.
Any help anyone can give would be greatly appreciated. Thank you much!
Ren Flot
March 5, 2004 at 12:22 pm
You will have to reinitalize your log shipping apply the last full diffs and tlogs to get you current and extend your retention time. Personally, I don't use MS log shipping and don't know many people who do. I would look into custom log shipping scripts written by several people. There are some in the scripts section on this site.
Wes
March 5, 2004 at 1:10 pm
Burthold,
Thanks much. I really appreciate your reply. Great suggestion. Is using the scripts a more reliable remedy to getting the logs shipped? Do I have to know allot about scripting to get them to work?
Ren
March 5, 2004 at 1:26 pm
People have said great things about the logship scripts posted on this site. I've never used them, I have used the SQL Logshipping and not had any serious problems.
March 5, 2004 at 1:44 pm
stacenic,
Thank you very much for your input. It is greatly appreciated.
I was under the same impression when I was preparing to use MS log shipping, but now that I've been working with it for a couple of weeks, I'm having these issues. Granted, I have 14 other db's where the log shipping configured is working fine, but these four particular db's have been troublesome for some reason.
I'm not sure which approach I'm going to take in solving this, I may try the scripts but I'm very new to SQL server and that may be cumbersome for a time. I know one thing, it's Friday and the day is almost done, so this will be addressed on Monday.
Thanks again and have a great weekend.
Ren
March 5, 2004 at 1:47 pm
Things always look different on a Monday...I would not think about it at the weekend and then come back to it on Monday.
A parting thought is that if it's working for the other db's then it should work for those 4. Increase the retention time on the primary server so that you are able to hold the logs longer which should prevent the trouble of the logs being too late to apply on the far end.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply