|
I am running SQL Server 2005 sp3. I do a backup with
(comments are locked)
|
|
How big is the backup? Assuming it's less than a 1TB this command usually returns extremely quickly. Can you see if it's blocked by a process or if it's waiting for something? Use sys.dm_exec_requests to see the processes that are currently running. Database is VERY small. Nothing is blocking it
Aug 07 '12 at 10:25 PM
BillBusking
Is there a wait state for the process? There must be some indication why things are running long.
Aug 08 '12 at 09:50 AM
Grant Fritchey ♦♦
(comments are locked)
|


Is this a user database or system, not that it should matter? Does it happen on any backup file you try or just a particular one?
Did you try restoring the backup? How much time that takes? What are the wait stats at the time of verifying? Can you please share the actual command you are running?
BTW, With checksum the restore verifyonly does take a bit more time.
But most importantly do not take this command as a reliable resource. The best way to verify a backup is to restore it.
did not try to restore because the restore verifyonly command never ended. Commands used were BACKUP DATABASE [ACS] TO DISK = N'H:SQLBK2FSMCKSQL3VS1ACSFULLfile_name.bak' WITH CHECKSUM and then run RESTORE VERIFYONLY FROM DISK = N'H:SQLBK2FSMCKSQL3VS1ACSFULLfile_name.bak'