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.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Log Shipping - Restore Error

Author  Topic 

maximus_vj
Yak Posting Veteran

88 Posts

Posted - 2004-08-10 : 14:38:22
Hello,

I have implemented Log Shipping and it seems to work fine apart from some errors. I changed some records on Primary Server and after a while it propagtes to the secondary Server.

My Log Shipping monitor doesn't show out of sync.

But when I see "View Copy/Restore History" and then select a Load Activity at 10 AM, it shows this on the Message part:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'D:\secondarydoctlogs\Documents_tlog_200408101000.TRN'. Device error or device off-line. See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.

And the Load Activity is like this:
Activity : Load
Status / Error : Succeeded
# Files : 6
Last File:Documents_tlog_200408101000.TRN

On the Secondary Server I saw the Log and this is what happens:
First I got this message:

BackupDiskFile::OpenMedia: Backup device 'D:\secondarydoctlogs\Documents_tlog_200408101000.TRN' failed to open. Operating system error = 32(The process cannot access the file because it is being used by another process.).

And after this it will start restoring again trans logs from 8:45 to 10 and this time the trans log at 10:00 is restored successfully. (It already finished restoring 8:45 through 9:45)

And I looked at teh Restore Job on the secondary Server and it shows as if it succeeded.

My question is why I am getting these messages on the Monitor Server and on the Secondary Server. Am I getting these messages because any transaction logs are misseed while restoring? Any help is appreciated.


Thanks,
Maximus





tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-08-10 : 15:20:37
This happens when the copy job is still running and the restore job is trying to restore the TRN file. It can't do it until the copy job has completed. The next time the restore runs, it will catch that one if the copy job is now done. The restore job can handle more than one TRN file, so if there are a few for it to do, it will do it all in that one job.

Tara
Go to Top of Page

maximus_vj
Yak Posting Veteran

88 Posts

Posted - 2004-08-10 : 15:29:12
Thanks Tara
Go to Top of Page
   

- Advertisement -