Video Screencast Help

MSSQL 2008 Backup Status 2 & 29

Created: 05 Sep 2012 • Updated: 05 Sep 2012 | 4 comments

I have Netbackup setup to backup a few file servers and a MS SQL 2008 DB server. It has been working fine for a long time, and suddenly it failed with status (2) since 2 days back. I've exhausted this forum and found a lot of similar error, but none of the solution works for my case. Another missing clue is that I can't find <install_path>\NetBackup\logs \dbclient\<date>.LOG , other logs is available, such as user_ops\mssql ... etc.

SQL Server: stars01prddb04 (it's a cluster consisting of db01 and db02)

Master/Media Server: stars01prdbk01

So I decided to throw my unique problem here and see if there's anyone with a solution

Followings is the job status from Activity Monitor (Transaction Log backup also display similar error)

 

9/4/2012 12:12:14 AM - Info nbjm(pid=3152) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=93065, request id:{1BDD5A7A-58DF-4DC4-B37D-2DDE9B7EFDAC})  
9/4/2012 12:12:14 AM - requesting resource Backup_SAN_F_Drive
9/4/2012 12:12:14 AM - requesting resource stars01prdbk01.NBU_CLIENT.MAXJOBS.stars01prddb04
9/4/2012 12:12:14 AM - requesting resource stars01prdbk01.NBU_POLICY.MAXJOBS.Daily_SQL_DB_FULL_0030_0130
9/4/2012 12:12:14 AM - granted resource stars01prdbk01.NBU_CLIENT.MAXJOBS.stars01prddb04
9/4/2012 12:12:14 AM - granted resource stars01prdbk01.NBU_POLICY.MAXJOBS.Daily_SQL_DB_FULL_0030_0130
9/4/2012 12:12:14 AM - granted resource Backup_SAN_F_Drive
9/4/2012 12:12:14 AM - estimated 0 Kbytes needed
9/4/2012 12:12:14 AM - Info nbjm(pid=3152) started backup job for client stars01prddb04, policy Daily_SQL_DB_FULL_0030_0130, schedule Full on storage unit Backup_SAN_F_Drive
9/4/2012 12:12:15 AM - started process bpbrm (8016)
9/4/2012 12:12:16 AM - connecting
9/4/2012 12:12:18 AM - connected; connect time: 00:00:02
9/4/2012 12:14:23 AM - Error bpbrm(pid=8016) from client stars01prddb04: ERR - command failed: none of the requested files were backed up (2)
9/4/2012 12:14:23 AM - Error bpbrm(pid=8016) from client stars01prddb04: ERR - bphdb exit status = 2: none of the requested files were backed up
9/4/2012 12:14:28 AM - end writing
none of the requested files were backed up(2)
9/4/2012 12:14:33 AM - Info bphdb(pid=992) done. status: 2: none of the requested files were backed up  
The status changes to 29 yesterday when I start the backup manually with the following error:
9/4/2012 8:17:24 PM - Info nbjm(pid=6608) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=93083, request id:{6F30C605-D4E1-4153-BEE0-10C9E6F91E7E})  
9/4/2012 8:17:24 PM - requesting resource Backup_SAN_F_Drive
9/4/2012 8:17:24 PM - requesting resource stars01prdbk01.NBU_CLIENT.MAXJOBS.stars01prddb04
9/4/2012 8:17:24 PM - requesting resource stars01prdbk01.NBU_POLICY.MAXJOBS.Daily_SQL_DB_FULL_0030_0130
9/4/2012 8:17:25 PM - granted resource stars01prdbk01.NBU_CLIENT.MAXJOBS.stars01prddb04
9/4/2012 8:17:25 PM - granted resource stars01prdbk01.NBU_POLICY.MAXJOBS.Daily_SQL_DB_FULL_0030_0130
9/4/2012 8:17:25 PM - granted resource Backup_SAN_F_Drive
9/4/2012 8:17:25 PM - estimated 0 Kbytes needed
9/4/2012 8:17:25 PM - Info nbjm(pid=6608) started backup job for client stars01prddb04, policy Daily_SQL_DB_FULL_0030_0130, schedule Full on storage unit Backup_SAN_F_Drive
9/4/2012 8:17:25 PM - started process bpbrm (10004)
9/4/2012 8:17:26 PM - connecting
9/4/2012 8:17:29 PM - Info bpbrm(pid=10004) starting bphdb on client         
9/4/2012 8:17:29 PM - Info bphdb(pid=9492) Backup started           
9/4/2012 8:17:29 PM - connected; connect time: 00:00:03
9/4/2012 8:17:30 PM - Error bpbrm(pid=10004) from client stars01prddb04: ERR - failed executing command <"I:\STARS01PRDDB04_FULL_Backup.bch">    
9/4/2012 8:17:30 PM - Error bpbrm(pid=10004) from client stars01prddb04: ERR - exit status: <-1>     
9/4/2012 8:17:30 PM - Error bpbrm(pid=10004) from client stars01prddb04: ERR - bphdb exit status = 29: failed trying to exec a command
9/4/2012 8:17:35 PM - end writing
failed trying to exec a command(29)
9/4/2012 8:17:40 PM - Info bphdb(pid=9492) done. status: 29: failed trying to exec a command    
 

The backup script looks fine. To test, I've started a manual backup on the SQL server itself, backing up "master" DB, and got this from the Netbackup MSSQL Client status

 

OPERATION BACKUP
DATABASE "master"
SQLHOST "STARS01PRDDB04"
NBSERVER "STARS01PRDBK01"
MAXTRANSFERSIZE 6
BLOCKSIZE 7
BROWSECLIENT "STARS01PRDDB04"
NUMBUFS 2
SQLCOMPRESSION TRUE
ENDOPER TRUE
 
ERR - Error in CDBbackrec::CDBbackrec: 6.
    CONTINUATION: - The system cannot find the file specified.
ERR - Error in VxBSASetEnv(NBBSA_CLIENT_HOST): 6.
    CONTINUATION: - The handle used to associate this call with a previous VxBSAInit() call is invalid.
INF - Results of executing <D:\Program Files\Veritas\NetBackup\dbext\mssql\temp\__18_32_37_614_00.bch>: 
<0> operations succeeded. <1> operations failed.
INF - The following object(s) were not backed up successfully.
INF - master
From the MSSQL Client Status, it return error (-1) for backup using script, and error (31073) for backup using "Backup SQL Server Object"
 
I've done various checking using bpclntcmd and found no problem. Did telnet test on the 3 ports, also no problem. Firewall is turn off on both servers.
 
I think the first clue to this should lie on <install_path>\NetBackup\logs \dbclient\<date>.LOG , how do I turn it on?
 
Any help is greatly appreciated
 

Comments 4 CommentsJump to latest comment

Will Restore's picture

edit the script, remove this line:

 SQLCOMPRESSION TRUE
 
 
 

create the logs directory:

 mkdir D:\Program Files\Veritas\NetBackup\logs\dbclient

 

Will Restore -- where there is a Will there is a way

faulty's picture

Thank wr,

Now i'm getting this in dbclient log

 

10:12:04.597 [12204.11796] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6635: 0: fopen() failed: 2 0x00000002
10:12:04.597 [12204.11796] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6636: 0: fopen() failed: D:\Program Files\Veritas\NetBackup\var\host_cache\157\b8a47d57+veritas_pbx,1,0,2,1,0+stars01prdbk01.txt
10:12:04.613 [12204.11796] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6635: 0: fopen() failed: 2 0x00000002
10:12:04.613 [12204.11796] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6636: 0: fopen() failed: D:\Program Files\Veritas\NetBackup\var\host_cache\07a\5f2d2a7a+0,1,2,0,1,0+10.66.8.17.txt
10:12:04.628 [12204.11796] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6635: 0: fopen() failed: 2 0x00000002
10:12:04.628 [12204.11796] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6636: 0: fopen() failed: D:\Program Files\Veritas\NetBackup\var\host_cache\157\b8a47d57+vnetd,1,0,2,1,0+stars01prdbk01.txt
10:12:04.628 [12204.11796] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6635: 0: fopen() failed: 2 0x00000002
10:12:04.628 [12204.11796] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6636: 0: fopen() failed: D:\Program Files\Veritas\NetBackup\var\host_cache\157\b8a47d57+bprd,1,0,2,1,0+stars01prdbk01.txt
10:12:04.644 [12204.11796] <2> vnet_pbxConnect: pbxConnectEx Succeeded
10:12:04.644 [12204.11796] <2> logconnections: BPRD CONNECT FROM 10.66.8.13.65356 TO 10.66.8.17.1556 fd = 784
10:12:04.987 [12204.11796] <16> bsa_checkFeatureId: None of the feature(s) are licensed
10:12:04.987 [12204.11796] <16> VxBSAInit: ERR - The license for the requested feature is not available.
10:12:28.935 [7264.4704] <2> vnet_pbxConnect: pbxConnectEx Succeeded
10:12:28.935 [7264.4704] <2> logconnections: BPRD CONNECT FROM 10.66.8.13.65378 TO 10.66.8.17.1556 fd = 744
10:12:29.262 [7264.4704] <16> bsa_checkFeatureId: None of the feature(s) are licensed
10:12:29.262 [7264.4704] <16> VxBSAInit: ERR - The license for the requested feature is not available.
We have proper license in place, and it's not expiring any time soon. What could be the cause of this? File based backup is working fine so far.
 
Mark_Solutions's picture

Sounds just like this one ...

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

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

faulty's picture

Sorry guys, it was my bad. The license for MSSQL Server Extension has expired. It has different license key as the Backup Server itself, which I have updated few months back.

Thanks for all helpful input