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 |
|
admin001
Posting Yak Master
166 Posts |
 Posted - 2003-09-05 : 02:47:15
|
| Hi ,Well I have just setup Logshipping between two servers to test which are running under same domain account . As per standards i created a Logshipping through Database Maintenance plan . Everything went well initially and the plan was also created successfully . Database was created on the Sec. server with Read-only . Not until I got a red cross during the logshipping restore job . I checked my Logshipping monitor server for the error which was as follows :Error 4326: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set terminates at LSN 6000000042300001, which is too early to apply to the database. A more recent log backup that includes LSN 7000000013900001 can be restored.[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.I tried to figure out what this means but nowhere could i get any hints to resolve this . Then I tried to create the plan again with slightly increasing the copy / load schedule , but no success .I am sure many of us would have faced this problem so i need your suggestions to get this fixed . Both my servers are SQL 2000 Enterprise Edition with SP 3a . Also wanted to check whether both the SQL servers can run under different Domain accounts . Thanks for you help . |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-09-05 : 11:47:27
|
| The error that you are getting means that the log that is trying to be applied isn't the correct log. The message means that there is an older log that needs to be applied first. When you start setting up log shipping, make sure that the log shipping directories are empty, meaning no files. After log shipping has been setup, manually kickoff the transaction log backup job. Check the file name that was used. Then kickoff the copy job. Check to see if the correct file was copied. Then kickoff the restore job. Check to see if the restore was successful. You could also take a look at the log shipping monitor to see this stuff. For some reason, your log shipping got out of sync.Tara |
 |
|
|
|
|
|
Logshipping restore error .