SQL Server - VERIFY DATABASE is terminating abnormally.

Asked By Kanagasabapathy T on 27-Apr-10 05:36 AM
Hi,
I took a log backup to a dump location ( created using BACKUP DEVICE under Server Objects ) which resides in some other network server.
When I do RESTORE VERIFYONLY ( SQL SERVER 2005 with SP2 )to test the feasibility of restoring this log file , I'm getting the below error :

Msg 3203, Level 16, State 2, Line 1
Read on "\\172.XX.XX.X\F$\Database\Reporter_Log.bak" failed: 1130(error not found)
Msg 3013, Level 16, State 1, Line 1
VERIFY DATABASE is terminating abnormally.

My concern is whether it is throwing out an error due to following reasons:

1. Log size is 28 GB and Log backup size is around 30 GB (Recovery model: FULL ) due to which RESTORE VERIFYONLY is failing out. ( I'm executing the command on Source server and not on the dump server where we have not installed SQL server ).

2. What should be the file extension when we create a BACKUP DEVICE for LOG Backup ( By default it takes the Device name.bak )

Let's say :   Device Name : Reporter_Log
                 Destination    : \\172.XX.XX.X\F$\Database\Reporter_Log.bak

Pls let me know on this.

Thanks,
Kanagasabapathy.
               


Web Star replied to Kanagasabapathy T on 27-Apr-10 05:41 AM
try this
You'll need to run RESTORE FILELISTONLY in order to work this out:

RESTORE FILELISTONLY
FROM DISK = 'C:\Backup.BAK'
and have a look http://support.microsoft.com/kb/290787
Kanagasabapathy T replied to Web Star on 27-Apr-10 06:44 AM
Hi Web Star,

I'm getting proper output for RESTORE FILELISTONLY and RESTORE HEADERONLY but why not with RESTORE VERIFYONLY. ( Whether it is due to log backup file size ( aroung 30 GB ) or Network server dump location )


Thanks,
Kanagasabapathy.