Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

SQL Server 2005 restore fails

Updated: 21 May 2010 | 7 comments
prichard@blm.gov's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Environment:
Master:  AIX 5.3 running Netbackup 6.5.1
Media Server: Windows 2003 Server running Netbackup 6.5.1
Netbackup client:Windows 2008 Server, 64 bit running 64 bit Netbackup 6.5.4

Backups of SQL Server 2005 complete with no errors.

When I attempt a restore with the NB DB extension GUI it appears to start on the client but never shows up in the Activity Monitor.  I attempt the restore with the following generated bch file that I added TRACELEVEL MAX to:
 

OPERATION RESTORE
OBJECTTYPE DATABASE
DATABASE "sde"
# The following image is type: Full
NBIMAGE "ilmmtso3db8.MSSQL7.ILMMTSO3DB8.db.sde.~.7.001of001.20091127102757..C"
SQLHOST "ilmmtso3db8"
NBSERVER "ILMMTSO0DB38"
BROWSECLIENT "ILMMTSO3DB8"
MAXTRANSFERSIZE 6
BLOCKSIZE 7
RESTOREOPTION REPLACE
RECOVEREDSTATE NOTRECOVERED
NUMBUFS 2
TRACELEVEL MAX
ENDOPER TRUE

It takes about 10 minutes before the errors occur, I get the following status:

<batch file in previous text>

INF - RESTORE STARTED USING
Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
Nov 24 2008 13:01:59
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 6.0 (Build 6002: Service Pack 2)
Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\rest.bch, Op# = 1.
INF - Using backup image ilmmtso3db8.MSSQL7.ILMMTSO3DB8.db.sde.~.7.001of001.20091127102757..C
INF - restore database "sde" from VIRTUAL_DEVICE='VNBU0-3568-808-1259350968' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, replace , norecovery
INF - Number of stripes: 1, Number of buffers per stripe 2.
INF - Created VDI object for SQL Server instance <ilmmtso3db8>. Connection timeout is <300> seconds.
Restore started Fri Nov 27 12:42:50 2009

ERR - Error in VxBSAGetObject: 3.
    CONTINUATION: - System detected error, operation aborted.
ERR - Error in VDS->Close: 0x8077000d.
ERR - Error in GetCommand: 0x80770004.
    CONTINUATION: - All devices are open
    CONTINUATION: - An abort request is preventing anything except termination actions.
INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\rest.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 918(918) seconds.
INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\rest.bch>:
<0> operations succeeded. <1> operations failed.

Any ideas?

 

Comments

dubplate's picture
27
Nov
2009
1 Vote +1
Login to vote

 This could be completely

 This could be completely unrelated but it's important to note that I don't believe running a NBU 6.5.4 client is supported when backing up to a 6.5.1 master and media server. At a minimum the master has to be on the  same release or higher (6.5.4 in this case) and I believe the media server as well in order to support 6.5.4 clients.

rjrumfelt's picture
27
Nov
2009
1 Vote +1
Login to vote

Not sure if the client/master server

version level mismatch is the issue here (but it is never recommended to have clients running at a newer version than the master)

Are the logs you pasted above the dbclient logs, or are they just what you get from the GUI?  If those are just from what comes from the GUI, if possible, try to get the dbclient logs and post them here.  

rj_nbu's picture
28
Nov
2009
0 Votes 0
Login to vote

32 bit SQL on 64 bit OS

Have you installed the compatibility patch ? Check if there are any events from SQLVDI source in the Event Viewer

GENERAL ERROR: Attempts to back up 32 bit SQL on a 64 bit Windows server fail with a CoCreateInstance error message in the dbclient log file.

http://seer.entsupport.symantec.com/docs/283790.htm

-Rajeev
"Unix IS user friendly... It's just selective about who its friends are"

Marianne van den Berg's picture
28
Nov
2009
1 Vote +1
Login to vote

I agree with everyone else -

I agree with everyone else - a client should never be at a higher patch level that the Master and media server.
Fact is - your backup worked.
What errors can be seen in dbclient log?
Also have a look at bprd log on the master server if request from client is received.

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

fieldnmultistream's picture
28
Nov
2009
0 Votes 0
Login to vote

Please; post your dbclient

Please; post your dbclient logs.  And as Marianne stated, the backup worked - I think if there were any incompatibility issues, we would have seen them at the backup level.

prichard@blm.gov's picture
30
Nov
2009
0 Votes 0
Login to vote

Thank you for your excellent

Thank you for your excellent help.  I have been pulled into another project so I won't be able to respond in depth until tomorrow evening.

-Park

prichard@blm.gov's picture
10
Dec
2009
0 Votes 0
Login to vote

All, Thank you for your

All,

Thank you for your useful advice.  I upgraded my master, media, and admin client to 6.5.4 and the restore worked flawlessly. 

-Park