June 2, 2009 at 10:18 am
I'm trying to restore a database on a SQL2k5 Express instance. The database is from a SQL2k instance. I believe the backup may have been made using a 3rd party tool, and possibly made to tape.
Follows is my restore command:
RESTORE DATABASE TCDurham
FROM Disk = 'D:\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\TCDurham_db_200809260200.bak'
WITH
Replace,
MOVE 'TCDurham' TO 'D:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\TCDurham.mdf',
MOVE 'TCDurham_Log' TO 'D:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\TCDurham_log.ldf',
Continue_After_Error
The restore runs for a little over a minute & then gives these messages:
The file "TCDurham_Data" is selected. At the time of backup it was known by the name "TCDurham". RESTORE will continue operating upon the renamed file.
Msg 3242, Level 16, State 2, Line 1
The file on device 'D:\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\TCDurham_db_200809260200.bak' is not a valid Microsoft Tape Format backup set.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
The Continue_After_Error is intentional. When I initially tried to restore the database with the GUI tool in MSSMS, I received an error: 'detected an error on page(0:0) in database TCDurham as read from the backup set'.
I know what a tape backup is, but since I don't use them, I'm not familiar with the ins & outs of them. Assuming the backup (now on disk) was originally made to tape, is there a way to force this restore?
Thanks,
BigSam
June 2, 2009 at 11:17 am
Do you get any results from the contents of the backup file try the following to verify the backup:-
restore FILELISTONLY from disk =
'D:\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\TCDurham_db_200809260200.bak'
June 2, 2009 at 11:40 am
Yes.
Basically it confirms the information I already had: logical name, physical name.
I was surprised to see that the file group name for the log was Null (rather than Primary), but that shouldn't matter, since I created the new database with Simple Recovery.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply