Restoring MSDB - e0008492 - Database Query Failure

Job name            : Restore 00083
Job type            : Restore
Job status          : Failed
Job log             : C:\Program Files\VERITAS\Backup Exec\NT\Data\BEX_XXXXXX_00785.xml
Server name         : XXXXXX
Selection list name : Restore 00072

Device name         : Backup-to-Disk Device 1
Target name         : All Devices (XXXXXXX)
Media set name      : 

Error category    : Resource Errors
Error             : e0008492 - Database Query Failure. See the job log for details.

For additional information regarding this error refer to link V-79-57344-33938

Original start time : 09 July 2013 15:58:27
Job started         : 09 July 2013 15:58:31
Job ended           : 09 July 2013 16:17:07
Elapsed time        : 00:18:36

Files               : 0
Directories         : 0
Skipped files       : 1
Corrupt files       : 0
Files in use        : 0

Byte count          : 0 bytes
Job rate            : -1.00 MB/Min (Byte count divided by Elapsed time for job)

Set type               : Restore
Set status             : Completed
Set description        : 

Resource name          : \\XXXXX\
Logon account          : XXXX\XXXXXX

Error                  : e0008492 - Database Query Failure. See the job log for details.

Agent used                     : Yes
Advanced Open File Option used : No
Image used                     : No

Start time             : 09 July 2013 15:59:05
End time               : 09 July 2013 16:17:07

Files                  : 0
Directories            : 0
Skipped files          : 1
Corrupt files          : 0
Files in use           : 0

Byte count             : 0 bytes
Rate                   : 0.00 MB/Min

Media used             : B2D028031

There actually are a lot of technotes available to help you troubleshoot and fix this issue. However, as you had mentioned disk failure, Have you confirmed if the SQL instance you are restoring to is the same version or later than the one you backed up from? Also, in the event viewer are you seeing any errors with relation to SQL VDI?

See if any of the below are aplicable and help

http://www.symantec.com/docs/TECH72460

http://www.symantec.com/docs/TECH35815

http://www.symantec.com/docs/TECH67379

http://www.symantec.com/docs/TECH28134

Hi Jay,

I am the same version of SQL Server - fortunately the data was replicated to a hosted server. Which was the exact same version - so I was able to get the version number very easily which meant the master restored easily!

I don't understand the SQL VDI comment - can you expand please?

I was following this article http://www.symantec.com/business/support/index?page=content&id=TECH22575 which is not quite the same as our version of backup exec but is a good start.

Will review your links and respond back in 5

Thanks

The technote that you are using should certainly be helpful. Also, on a quick thought, could you check if the database files are readonly (look in the OS)

What I meant was in the Windows event viewer, you might get some errors/warnings about SQLVDI corresponding to the restore. If we have something like this it would be helpful to troubleshoot as the 'database query failure' is a very generic error.

http://www.symantec.com/docs/TECH72460

This gives me 3 subsequent links

http://www.symantec.com/business/support/index?page=content&id=TECH64494

I am not seeing anything different in the Application Log other than what I see on screen in veritas

http://www.symantec.com/business/support/index?page=content&id=TECH35815

I am not sure how to check the MDACs are in sync as the old server is not able to boot, but everything else looks good!

http://www.symantec.com/business/support/index?page=content&id=TECH28134

There is over 100GB of disk space, and the MSDB database is under 30Mb!

Hi Jay,

the files were not read only.

Also one quick note - I have moved the server to our central location, however it can communicate with the new database server without issue.

Thanks

David

SQL VDI - I have managed to find errors! No idea what this means!!

SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=1012. Thread=1792. Client. Instance=. VD=Global\msdb_00__758d2135_9c75_44f7_8bb3_6573cebc180a__SQLVDIMemoryName_0.

my replies are a bit mesy but I have found SQLVDI errors, have never seen one of these before! So will run away and do some research, but this is all new to me!

Thanks

Hi Jay,

Found the following link via asking 4th line support (aka Google)

http://support.microsoft.com/kb/934396

However I am struggling to find the file for 2000, when I click get hotfix I am presented with a list that only list 2005 under product.http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=934396&kbln=en-us

Ok keeps not posting my replies!! Annoying!

I found the below link which sounds perfect
http://support.microsoft.com/kb/934396#appliesto

But the hotfix link does not include a fix for 2000 only 2005!