Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Backup and Recovery Community Blog

Error 239 and 2 while SQL Server Restore

Created: 17 Jul 2011 • 2 comments
Zahid.Haseeb's picture
+1 1 Vote
Login to vote

Environment

Veritas Netbackup Server and Client Version = 7.1

OS of Veritas Netbackup Server = win2008

Product = SQL Server 2008 R2

OS of Client = win2008

Its two Node Cluster of SFHA Version 5.1 SP2

Problem

Restore Child job failed Status Code 239 and Parent job failed with Status Code 2

Script

OPERATION BACKUP

DATABASE "Data123"

SQLHOST "PrimaryNode"

NBSERVER "VERITAS-NBU"

MAXTRANSFERSIZE 6

BLOCKSIZE 7

ENDOPER TRUE

Activity monitor

  

Detail Status of Activity Monitor

7/17/2011 4:15:28 PM - Info nbjm(pid=3684) starting backup job (jobid=38054) for client ClusterSrv, policy Dotnet_Full, schedule Manual 

7/17/2011 4:15:28 PM - Info nbjm(pid=3684) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=38054, request id:{7565B0E3-6972-43A9-8EC1-4F3C738815A2}) 

7/17/2011 4:15:28 PM - requesting resource veritas--hcart-robot-tld-0

7/17/2011 4:15:28 PM - requesting resource veritas-.NBU_CLIENT.MAXJOBS.cluster

7/17/2011 4:15:28 PM - requesting resource veritas-.NBU_POLICY.MAXJOBS.Dotnet_Full

7/17/2011 4:15:28 PM - granted resource veritas-.NBU_CLIENT.MAXJOBS.cluster

7/17/2011 4:15:28 PM - granted resource veritas-.NBU_POLICY.MAXJOBS.Dotnet_Full

7/17/2011 4:15:28 PM - granted resource veritas--hcart-robot-tld-0

7/17/2011 4:15:28 PM - estimated 0 Kbytes needed

7/17/2011 4:15:28 PM - Info nbjm(pid=3684) started backup job for client db-cluster, policy Dotnet_Full, schedule Manual on storage unit veritas-hcart-robot-tld-0

7/17/2011 4:15:28 PM - started process bpbrm (5348)

7/17/2011 4:15:30 PM - Info bpbrm(pid=5348) db-cluster is the host to backup data from    

7/17/2011 4:15:30 PM - Info bpbrm(pid=5348) reading file list from client       

7/17/2011 4:15:30 PM - connecting

7/17/2011 4:15:33 PM - Info bpbrm(pid=5348) starting bphdb on client        

7/17/2011 4:15:33 PM - Info bphdb(pid=8020) Backup started          

7/17/2011 4:15:33 PM - connected; connect time: 00:00:03

7/17/2011 4:15:36 PM - Info dbclient(pid=13796) INF - BACKUP STARTED USING       

7/17/2011 4:15:36 PM - Info dbclient(pid=13796) Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)   

7/17/2011 4:15:36 PM - Info dbclient(pid=13796) Apr  2 2010 15:48:46       

7/17/2011 4:15:36 PM - Info dbclient(pid=13796) Copyright (c) Microsoft Corporation        

7/17/2011 4:15:36 PM - Info dbclient(pid=13796) Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) 

7/17/2011 4:15:36 PM - Info dbclient(pid=13796) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\Script1.bch, Op# = 1     

7/17/2011 4:15:36 PM - Info dbclient(pid=13796) INF - Using backup image PrimaryNode.MSSQL7.CLUSTER.db.DotNet.~.7.001of001.20110717161534..C      

7/17/2011 4:15:36 PM - Info dbclient(pid=13796) INF - backup database "DotNet" to VIRTUAL_DEVICE='VNBU0-13796-8740-1310901335' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 1

7/17/2011 4:15:36 PM - Info dbclient(pid=13796) INF - Number of stripes: 1, Number of buffers per stripe 1.

7/17/2011 4:15:36 PM - Info dbclient(pid=13796) INF - Created VDI object for SQL Server instance <db-cluster>. Connection timeout is <300> seconds.

7/17/2011 4:15:49 PM - Info dbclient(pid=13796) ERR - Error in VxBSACreateObject: 3.      

7/17/2011 4:15:49 PM - Info dbclient(pid=13796)     CONTINUATION: - System detected error, operation aborted. 

7/17/2011 4:15:54 PM - Info dbclient(pid=13796) ERR - Error in VDS->Close: 0x80770004.      

7/17/2011 4:15:54 PM - Info dbclient(pid=13796)     CONTINUATION: - An abort request is preventing anything except termination actions.

7/17/2011 4:15:54 PM - Info dbclient(pid=13796) INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\Sona.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 19(19) seconds.

7/17/2011 4:15:56 PM - Info dbclient(pid=13796) INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\Script1.bch>:     

7/17/2011 4:15:56 PM - Info dbclient(pid=13796) <0> operations succeeded. <1> operations failed.      

7/17/2011 4:15:56 PM - Info dbclient(pid=13796) INF - The following object(s) were not backed up successfully.  

7/17/2011 4:15:56 PM - Info dbclient(pid=13796) INF - DotNet         

7/17/2011 4:15:56 PM - Error bpbrm(pid=5348) from client cluster: ERR - command failed: none of the requested files were backed up (2)

7/17/2011 4:15:56 PM - Error bpbrm(pid=5348) from client cluster: ERR - bphdb exit status = 2: none of the requested files were backed up

7/17/2011 4:15:58 PM - end writing

7/17/2011 4:16:03 PM - Info bphdb(pid=8020) done. status: 2: none of the requested files were backed up 

none of the requested files were backed up(2)

What I was doing wrong

I was not using Virtual Name in entering to Netbackup Database Extension. In the SQL Server properties enter Host box I was entering the physical Node Name. See the following snao for reference.

Resolution

I simply used the Virtual Name and then made the script and then my Restore was successful. See the new script for reference. Its has few more lines in the Script.

OPERATION BACKUP

DATABASE "DotNet"

SQLHOST "cluster"

NBSERVER "veritas-"

BROWSECLIENT "cluster"

MAXTRANSFERSIZE 6

BLOCKSIZE 7

ENDOPER TRUE

Comments 2 CommentsJump to latest comment

StanJones's picture

I had been searching for the solution to this problem since two weeks for one of the customers. I am absolutely relieved to have found it in your write-up. Thanks a lot for the help.

Regards,

Stan

-2
Login to vote
Zahid.Haseeb's picture

Great to hear that your problem is resolved :) 

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

zahidhaseeb.wordpress.com

+7
Login to vote