Video Screencast Help

SQL 2005 Restore Failing with DBBACKEX Has stoped working.

Created: 24 Nov 2010 | 6 comments

Hi All, 

I Several SQL 2005 Databases on a Windows 2008 Server (x64).  Netbackup SQL agent on that server is 6.5.4.

I am trying to restore these databases to another Windows 2008 Server (x64) again with SQL 2005.  Using the Netbackup SQL Agent (Version 7.0)

The Master Server is version 7.0 (Build 20100104)

When i attempt the restore using the following Script created with the SQL Agent:

DATABASE "SharePoint_Config_PHS"
# The following image is type: Full
NBIMAGE "GCAS006.MSSQL7.GCAS006.db.SharePoint_Config_PHS.~.7.001of001.20101123180316..C"
BROWSECLIENT "GCAS006.phsgroup.local"

After around 10 minutes i get the following:

Microsoft SQL Server 2005 - 9.00.1399.06 (X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.0 (Build 6002: Service Pack 2)
Batch = C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\__11_22_03_748_00.bch, Op# = 1.
INF - Using backup image GCAS006.MSSQL7.GCAS006.db.SharePoint_Config_PHS.~.7.001of001.20101123180316..C
INF - restore database "SharePoint_Config_PHS" from VIRTUAL_DEVICE='VNBU0-2796-1568-1290597725' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, norecovery
INF - Number of stripes: 1, Number of buffers per stripe 2.
INF - Created VDI object for SQL Server instance <GCAS496>. Connection timeout is <300> seconds.
Restore started Wed Nov 24 11:22:07 2010

ERR - Error in VxBSAGetObject: 3.
    CONTINUATION: - System detected error, operation aborted.
ERR - Error in VDS->Close: 0x8077000d.
    CONTINUATION: - All devices are open
INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\__11_22_03_748_00.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 1090(1090) seconds.

Accompanied by the following Dialogue box:

DBBACKEX MFC Application has stopped working


Problem signature:

Problem Event Name: BEX64

Application Name: dbbackex.exe

Application Version: 7.0.2010.104

Application Timestamp: 4b42a075

Fault Module Name: sqlvdi.dll_unloaded

Fault Module Version:

Fault Module Timestamp: 433c8f44

Exception Offset: 0000000034518223

Exception Code: c0000005

Exception Data: 0000000000000008

OS Version: 6.0.6002.

Locale ID: 2057

Additional Information 1: 3ab1

Additional Information 2: 88b83ead7b674132aa2e1ea60e820cfb

Additional Information 3: 39cc

Additional Information 4: 7f52bdc20c877f9237da9ca82db20e89

And the Evenlog Says the following in relation to the above:

Faulting application dbbackex.exe, version 7.0.2010.104, time stamp 0x4b42a075, faulting module sqlvdi.dll_unloaded, version, time stamp 0x433c8f44, exception code 0xc0000005, fault offset 0x0000000034518223, process id 0xaec, application start time 0x01cb8bc9d1f6b376.

So far im Stumped!  Have i missed something obvious?  This apears to effect all the databases i want to restore from the original server.

Thanks in advance.


Comments 6 CommentsJump to latest comment

Zahid.Haseeb's picture

Follow the below link it may hopefully help you to restore SQL database to an alternate location.

Any comment will be appreciated. Mark as Solution if your query is resolved
Thanks in Advance
Zahid Haseeb

Riaan.Badenhorst's picture

IMHO you're going to have match the NetBackup Client versions on source and destination


Riaan Badenhorst

ITs easy :)

Marianne's picture

Always increase Client Read Timeout to at least 2 hours (7200) when restoring large databases.

Please also enable dbclient log on the destination client.

(I assume you've opened GUI's with right-click, run as Administrator? I have seen weird and wonderful errors when I forgot to do that...)

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Abesama's picture

it's strange that dbbackex is faulting after successfully talking to SQL instance to create a VDI object.

yes it could be the binary itself - so just double check your NBU version and it's patch version on GCAS496 is the same as the NBU version on GCAS006.

another thing I can think of is, because you are not using the "move script," that you have to make sure there are same disk drive letter and paths for the database file and the log files as on the source SQL host GCAS496 - say you had your SQL database&log files on F:\SQL\data on the original SQL host, you need an F: drive on this destination SQL host, and the same path \SQL\data too.

if your database and log files were backed up from one drive:path and you want to restore it to another drive:path, then you need to use run what's called "move script" within NBU SQL restore operation.

as a last thing, if there are any hung dbbackex.exe/dbbackup.exe/dbclient.exe/tar32.exe from taskmgr then kill those before trying restore agian.

hope this helps, A

Anger Management

Zahid.Haseeb's picture

Yes you are right. I also recommand him alternate restore which as you said "move script".

Any comment will be appreciated. Mark as Solution if your query is resolved
Thanks in Advance
Zahid Haseeb

Marky D's picture

Cheers for the advice,  I will give it a try and let you all know how i get on.