October 21, 2009 at 8:10 am
I have an sql2005 installation and a mirror server. Many of my databases are already mirrored, and I went to add a new one now that it is up and ready for production. It is running fine on the primary server. Just like the others I did a full backup and a log backup.
On the mirror server I loaded the .bak with 'restore with no recovery'. No problem.
Then I went to restore the log file (using studio) and got the error (as soon as I try to select the file, it does not wait till I select the restore instance):
Cannot find table 0. (System.Data)
In case the backups were corrupt, I tried it today with new .bak and .trn and the exact same failure occurred.
I tried restoring the .trn from t-sql and got this error:
Msg 4038, Level 16, State 1, Line 1
Cannot find file ID 1 on device 'g:\temp\BACKUPFILENAME.trn'.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
Other dbs have been successfully restored to this machine (and subsequently mirrored). As recently as yesterday I had loaded and mirrored another db (and this db IS full logging option). What could be going on with this one?
...
-- FORTRAN manual for Xerox Computers --
October 22, 2009 at 11:48 am
October 22, 2009 at 12:04 pm
9.0.3042
...
-- FORTRAN manual for Xerox Computers --
October 28, 2009 at 2:21 pm
I have seen this before but cannot remember exactly what the problem was ...
What is the output when you run RESTORE VERIFYONLY against your log file?
What is the output when you run RESTORE FILELISTONLY against your log file?
What is the output when you run RESTORE HEADERONLY against your log file?
Maybe it is related to the database in the log file not being on the server you are restoring to. what's the output from the sql below?
use master
go
select*
fromsys.databases
go
October 29, 2009 at 7:02 am
I tried restore with verifyonly and fileleistonly. I got the same error from both:
Msg 4038, Level 16, State 1, Line 1
Cannot find file ID 1 on device 'g:\temp\asco_prod_meta.trn'.
Msg 3013, Level 16, State 1, Line 1
RESTORE FILELIST is terminating abnormally.
This is a db that changes only occasionally. I tried loading just the .bak on the theory that perhaps the .log files were empty, however when I tried to mirror I got error 1478 ("insufficient transaction log data") so that is not the problem.
...
-- FORTRAN manual for Xerox Computers --
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply