Desperate with SQL2000 Log Shipping , Out Of Sync

After try and error for several months, finally my SQL2000 LS works.

i gave my self a little celebration for that.

but after running well for a day, just one day !

this morning it give me Out of Sync.

error messages:

failure /4305

activity : Load

[Microsoft SQL-DMO (ODBC SQLState: 42000)]
Error 4305: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set
begins at LSN 7000000026200001, which is too late to apply to the database. An earlier
log backup that includes LSN 6000000015100001 can be restored.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.

activity : Copy

failure / 32

The process cannot access the file because it is being used by another process.

i just dont understand, how come the load & copy process failed, after it works for a day.

Hi toni,

Are you using SQL 2000 Standard or Enterprise? In short are you using the Enterprise log shipping feature or carrying out log shipping through scripts?

sk

|||

Hi SK,

I'm using SQL2000 Ent Edition feature , using the Log Shipping Wizard.

The database for this LS is about 40GB, so in this case we restore the database to target server.

we did the restore process using OVDP(open view data protector) and it worked fine for a day until it gave us Out of sync.

any troubleshooting steps will be appreciated.

thx

|||

Not sure i could help you out in this as i am using the Standard edition of SQL Server 2k. However i was interested in log shipping, by script that is, but failed to make it work..So i was curious to know about your setup...

I take it that your transaction logs are created on a shared drive which then is restored by the receiving Sql Server(target).. Could it be that the network connection was lost and it missed out on one of the logs in between?

This guess is based on the fact that it worked for a day and so there shouldnt be any reason why it fails unless there is a communication problem...

Hope someone else could point out the technicalities behind it...

sk

|||

//Could it be that the network connection was lost and it missed out on one of the logs in between?//

i'll observe that, but i wonder if the system itself already has the mechanism to react on that problems ?

try to reconfigure the LS , set the interval to 15 mins, lets see...

thx

|||

failed again, but this time i think i found it.

there is another job running trx backup to tape device, so the missing trx goes to tape.

rgds