cancel
Showing results for 
Search instead for 
Did you mean: 

Errors trying to backup SQL cluster

Katiebee
Level 4
Hi all,
 
Netbackup 7.1.0.6
SQL 2008 R2
Windows Server 2008 R2
Netbackup Client 7.1
 
From DBclient log:
 
11:56:01.526 [448.5832] <2> vnet_pbxConnect: pbxConnectEx Succeeded
11:56:01.526 [448.5832] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.57993 TO 192.168.150.9.1556 fd = 592
11:56:01.886 [448.5832] <4> CGlobalInformation::VCSVirtualNameList: INF - Veritas Cluster Server is not installed.
11:56:01.886 [448.5832] <1> CGlobalInformation::VCSVirtualNameList:     CONTINUATION: - The system cannot find the path specified.
11:56:01.887 [448.5832] <4> getServerName: Read server name from nb_master_config: NB Server name
11:56:01.887 [448.5832] <4> CDBIniParms::CDBIniParms: INF - NT User is Domain Account
11:56:01.903 [448.5832] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_448_5832_1>, SQL userid <Domain Account> handle <0x00ff93a0>.
11:56:18.029 [448.5832] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_448_5832_1>, SQL userid <Domain Account> handle <0x00ffa640>.
11:56:34.151 [448.5832] <4> CGlobalInformation::CreateDSN: INF - Error Creating ODBC data source name
11:56:34.151 [448.5832] <1> CGlobalInformation::CreateDSN:     CONTINUATION: - Component not found in the registry
11:56:34.155 [448.5832] <2> vnet_pbxConnect: pbxConnectEx Succeeded
11:56:34.155 [448.5832] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.58100 TO 192.168.150.9.1556 fd = 752
11:56:34.313 [448.5832] <16> CDBbackmain::LoadUserLogin: ERR - Internal error. See the dbclient log for more information.
11:56:34.315 [448.5832] <2> vnet_pbxConnect: pbxConnectEx Succeeded
11:56:34.316 [448.5832] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.58101 TO 192.168.150.9.1556 fd = 752
11:56:34.424 [448.5832] <32> CDBbackmain::LoadUserLogin: ERR - Error 1 has been returned from GetCurrentDSN
11:56:34.424 [448.5832] <4> CDBbackmain::dbbackup: INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\sqlfull.bch>: 
 
<0> operations succeeded. <0> operations failed.
 
From backup job details on the Netbackup Administrator console:
20/12/2013 11:56:01 - connected; connect time: 00:00:03
20/12/2013 11:56:34 - Info dbclient(pid=448)     CONTINUATION: - Component not found in the registry 
20/12/2013 11:56:34 - Info dbclient(pid=448) ERR - Internal error. See the dbclient log for more information.  
20/12/2013 11:56:34 - Info dbclient(pid=448) INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\sqlfull.bch>:      
20/12/2013 11:56:34 - Info dbclient(pid=448) <0> operations succeeded. <0> operations failed.       
20/12/2013 11:56:54 - Error bpbrm(pid=10892) from client Clustername: ERR - command failed: none of the requested files were backed up (2)
20/12/2013 11:56:54 - Error bpbrm(pid=10892) from client Clustername: ERR - bphdb exit status = 2: none of the requested files were backed up
20/12/2013 11:56:57 - end writing
 
When I tried to backup by running the script I can see the following errors in the status window:
 
ERR - Error in VxBSACreateObject: 3.
    CONTINUATION: - System detected error, operation aborted.
ERR - Error in GetCommand: 0x80770004.
    CONTINUATION: - An abort request is preventing anything except termination actions.
DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3202><[Microsoft][ODBC SQL Server Driver][SQL Server]Write on "VNBU0-3052-2108-1387555712" failed: 995(failed to retrieve text for this error. Reason: 15100)>.
DBMS MSG - SQL Message <3271><[Microsoft][ODBC SQL Server Driver][SQL Server]A nonrecoverable I/O error occurred on file "VNBU0-3052-2108-1387555712:" 995(failed to retrieve text for this error. Reason: 15105).>
DBMS MSG - SQL Message <3013><[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally.>
 
The script is;
 
OPERATION BACKUP
DATABASE $ALL
SQLHOST "Clustername"
NBSERVER "NB Servername"
MAXTRANSFERSIZE 3
BLOCKSIZE 7
POLICY Corp_Applications_SQL_NC_Full
NUMBUFS 2
RETRYTYPE AUTO
RETRYWAITSECONDS 60
NUMRETRIES 3
ENDOPER TRUE
 
and I get more info in the DBClient log:
 
16:08:28.824 [5308.6120] <4> StartupProcess: INF - C:\Program Files\Veritas\NetBackup\bin\dbbackex" -u Domain Account with sa roles -pw ***** -np -f "C:\Program Files\Veritas\NetBackup\DbExt\MsSql\sqlfull.bch"  
16:08:28.824 [5308.6120] <4> StartupProcess: INF - Starting: <C:\Program Files\Veritas\NetBackup\bin\dbbackex" -u Domain Account with sa roles -pw ***** -np -f "C:\Program Files\Veritas\NetBackup\DbExt\MsSql\sqlfull.bch"  >
16:08:28.872 [3052.3492] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:28.872 [3052.3492] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64915 TO 192.168.150.9.1556 fd = 588
16:08:29.307 [3052.3492] <4> CGlobalInformation::VCSVirtualNameList: INF - Veritas Cluster Server is not installed.
16:08:29.307 [3052.3492] <1> CGlobalInformation::VCSVirtualNameList:     CONTINUATION: - The system cannot find the path specified.
16:08:29.308 [3052.3492] <4> getServerName: Read server name from nb_master_config: NB Master
16:08:29.308 [3052.3492] <4> CDBIniParms::CDBIniParms: INF - NT User is KBadmin
16:08:29.322 [3052.3492] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3052_3492_1>, SQL userid <Domain Account with sa roles> handle <0x011193e0>.
16:08:29.335 [3052.3492] <4> CGlobalInformation::CreateDSN: INF - A successful connection to SQL Server <SQL Clustername\> has been made using standard security with DSN <NBMSSQL_3052_3492_1>
16:08:29.335 [3052.3492] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x011193e0>
16:08:29.335 [3052.3492] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3052_3492_1>, SQL userid <Domain Account with sa roles> handle <0x011193e0>.
16:08:29.344 [3052.3492] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x011193e0>
16:08:29.345 [3052.3492] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3052_3492_1>, SQL userid <Domain Account with sa roles> handle <0x011193e0>.
16:08:29.353 [3052.3492] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x011193e0>
16:08:29.354 [3052.3492] <4> CDBbackcat::GetVirtualServer: INF - Accessing database instance <SQL Clustername> on virtual server <SQL Clustername>.
16:08:29.354 [3052.3492] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3052_3492_1>, SQL userid <Domain Account with sa roles> handle <0x011193e0>.
16:08:29.373 [3052.3492] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x011193e0>
16:08:29.381 [3052.3492] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3052_3492_2>, SQL userid <Domain Account with sa roles> handle <0x011193e0>.
16:08:29.390 [3052.3492] <4> CGlobalInformation::CreateDSN: INF - A successful connection to SQL Server <SQL Clustername\> has been made using standard security with DSN <NBMSSQL_3052_3492_2>
16:08:29.390 [3052.3492] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x011193e0>
16:08:29.393 [3052.3492] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:29.393 [3052.3492] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64921 TO 192.168.150.9.1556 fd = 712
16:08:29.764 [3052.3492] <4> CDBbackmain::OperationsAreGroupable: INF - The batch file is not groupable because a standard policy type has been selected for backup.
16:08:29.771 [3052.3492] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3052_3492_3>, SQL userid <Domain Account with sa roles> handle <0x011193e0>.
16:08:29.780 [3052.3492] <4> CGlobalInformation::CreateDSN: INF - A successful connection to SQL Server <SQL Clustername\> has been made using standard security with DSN <NBMSSQL_3052_3492_3>
16:08:29.781 [3052.3492] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x011193e0>
16:08:29.781 [3052.3492] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3052_3492_3>, SQL userid <Domain Account with sa roles> handle <0x011193e0>.
16:08:29.791 [3052.3492] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x011193e0>
16:08:29.791 [3052.3492] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3052_3492_3>, SQL userid <Domain Account with sa roles> handle <0x011193e0>.
16:08:29.800 [3052.3492] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x011193e0>
16:08:29.801 [3052.3492] <4> CDBbackcat::GetVirtualServer: INF - Accessing database instance <SQL Clustername> on virtual server <SQL Clustername>.
16:08:29.803 [3052.3492] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:29.804 [3052.3492] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64925 TO 192.168.150.9.1556 fd = 732
16:08:30.157 [3052.3492] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:30.157 [3052.3492] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64926 TO 192.168.150.9.1556 fd = 732
16:08:30.495 [3052.3492] <4> CDBbackrec::CDBbackrec: INF - Use standard backup method with policy <Corp_Applications_SQL_NC_Full>.
16:08:30.497 [3052.3492] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:30.498 [3052.3492] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64927 TO 192.168.150.9.1556 fd = 732
16:08:32.024 [3052.2108] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3052_3492_3>, SQL userid <Domain Account with sa roles> handle <0x011196c0>.
16:08:32.037 [3052.2108] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x011196c0>
16:08:32.038 [3052.2108] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3052_3492_3>, SQL userid <Domain Account with sa roles> handle <0x0111ea10>.
16:08:32.047 [3052.2108] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x0111ea10>
16:08:32.047 [3052.2108] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3052_3492_3>, SQL userid <Domain Account with sa roles> handle <0x0111ea10>.
16:08:32.065 [3052.2108] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x0111ea10>
16:08:32.065 [3052.2108] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3052_3492_3>, SQL userid <Domain Account with sa roles> handle <0x0111ea10>.
16:08:32.079 [3052.2108] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x0111ea10>
16:08:32.079 [3052.2108] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3052_3492_3>, SQL userid <Domain Account with sa roles> handle <0x0111e940>.
16:08:32.090 [3052.2108] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x0111e940>
16:08:32.091 [3052.2108] <4> Dbbackrec::PerformNBOperation: INF - BACKUP STARTED USING
 
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4295.0 (X64) 
 
Oct 18 2013 19:22:52 
 
Copyright (c) Microsoft Corporation
 
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor) 
 
Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\sqlfull.bch, Op# = 1
16:08:32.095 [3052.2108] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:32.095 [3052.2108] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64933 TO 192.168.150.9.1556 fd = 864
16:08:32.215 [3052.2108] <4> InitPipeInfo: INF - Using backup image SQLNODENAME.MSSQL7.CLUSTERNAME.db.AdfsArtifactStore.~.7.001of001.20131220160830..C
16:08:32.218 [3052.2108] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:32.219 [3052.2108] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64934 TO 192.168.150.9.1556 fd = 868
16:08:32.335 [3052.2108] <4> Dbbackrec::CreateSQLcmdSyntax: INF - backup database "AdfsArtifactStore" to VIRTUAL_DEVICE='VNBU0-3052-2108-1387555712' with  stats = 10, blocksize = 65536, maxtransfersize = 524288, buffercount = 2
16:08:32.338 [3052.2108] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:32.338 [3052.2108] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64935 TO 192.168.150.9.1556 fd = 888
16:08:32.342 [3052.1964] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:32.342 [3052.1964] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64936 TO 192.168.150.9.1556 fd = 916
16:08:32.469 [3052.2108] <4> Dbbackrec::CreateSQLcmdSyntax: INF - Number of stripes: 1, Number of buffers per stripe 2.
16:08:32.659 [3052.2108] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:32.659 [3052.2108] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64937 TO 192.168.150.9.1556 fd = 916
16:08:32.788 [3052.2108] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3052_3492_3>, SQL userid <Domain Account with sa roles> handle <0x011198d0>.
16:08:32.800 [3052.2108] <4> CDBbackrec::InitDeviceSet(): INF - Created VDI object for SQL Server instance <SQL Clustername>. Connection timeout is <300> seconds.
16:08:32.803 [3052.2108] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:32.803 [3052.2108] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64939 TO 192.168.150.9.1556 fd = 1020
16:08:32.939 [3052.1964] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:32.939 [3052.1964] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64940 TO 192.168.150.9.1556 fd = 1044
16:08:34.598 [5308.6120] <8> CDBbackupView::ClassDropDownList: WARN - Error: bppllist not found in C:\Program Files\Veritas\NetBackup\bin\admincmd\bppllist.exe.
16:08:34.598 [5308.6120] <1> CDBbackupView::ClassDropDownList:     CONTINUATION: - The system cannot find the path specified.
16:08:34.598 [5308.6120] <8> CBatchDlg::OnInitDialog: WARN - Policy Dropdown not created: Server = NB Servername Client = SQL Node name
16:08:34.598 [5308.6120] <1> CBatchDlg::OnInitDialog:     CONTINUATION: - The system cannot find the path specified.
16:08:45.946 [3052.1964] <16> serverResponse: ERR - server exited with status 239: the specified client does not exist in the specified policy
16:08:45.946 [3052.1964] <16> CreateNewImage: ERR - serverResponse() failed
16:08:45.946 [3052.1964] <16> VxBSACreateObject: ERR - Could not create new image with file /SQL NODE NAME.MSSQL7.SQL CLUSTERNAME.db.AdfsArtifactStore.~.7.001of001.20131220160830..C.
16:08:45.946 [3052.1964] <4> getServerName: Read server name from nb_master_config: NB Servername
16:08:45.953 [3052.1964] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:45.953 [3052.1964] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64952 TO 192.168.150.9.1556 fd = 1032
16:08:46.178 [3052.1964] <16> writeToServer: ERR - send() to server on socket failed:
16:08:46.178 [3052.1964] <16> dbc_RemoteWriteFile: ERR - could not write progress status message to the NAME socket
16:08:46.178 [3052.1964] <4> getServerName: Read server name from nb_master_config: NB Servername
16:08:46.180 [3052.1964] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:46.181 [3052.1964] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64953 TO 192.168.150.9.1556 fd = 1032
16:08:48.188 [3052.1964] <16> writeToServer: ERR - send() to server on socket failed:
16:08:48.188 [3052.1964] <16> dbc_RemoteWriteFile: ERR - could not write progress status message to the NAME socket
16:08:48.188 [3052.1964] <16> DBthreads::dbclient: ERR - Error in VxBSACreateObject: 3.
16:08:48.195 [3052.1964] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:48.195 [3052.1964] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.64957 TO 192.168.150.9.1556 fd = 1032
16:08:52.922 [3052.1964] <1> DBthreads::dbclient:     CONTINUATION: - System detected error, operation aborted.
16:08:52.925 [3052.1964] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:08:52.925 [3052.1964] <2> logconnections: BPRD CONNECT FROM 192.168.150.14.65031 TO 192.168.150.9.1556 fd = 1032
16:08:53.765 [3052.1964] <8> close_image: Session being terminated abnormally, cleaning up
16:08:53.765 [3052.1964] <4> close_image: INF - backup FAILED
16:08:53.765 [3052.1964] <4> close_image: INF ---- end of Backup ---
 
 
but I have tried just using the SQL node name as well as the SQL cluster name with the same results.
 
Does anyone have any idea what is causing the errors? My colleague built the cluster for System Centre and would like to get the DBs backed up, but I'm really struggling to work out why its failing and to fix it.
 
Thanks in advance,
 
Katie 
1 ACCEPTED SOLUTION

Accepted Solutions

Mark_Solutions
Level 6
Partner Accredited Certified

This can be an issue on clusters

I assume you have set it up on both nodes and the script exists on both

If so in each bch file add an extra line:

BROWSECLIENT nodename

In that way it can have each nodes name it its own file

The policy should still have the virtual server name

View solution in original post

6 REPLIES 6

Katiebee
Level 4

Edit - I'm on Netbackup 7.1.0.3 not 7.1.0.6 as above! Sorry

Katie

Mark_Solutions
Level 6
Partner Accredited Certified

This can be an issue on clusters

I assume you have set it up on both nodes and the script exists on both

If so in each bch file add an extra line:

BROWSECLIENT nodename

In that way it can have each nodes name it its own file

The policy should still have the virtual server name

Will_Restore
Level 6

16:08:45.946 [3052.1964] <16> serverResponse: ERR - server exited with status 239: the specified client does not exist in the specified policy

 

add this to your SQL script file

BROWSECLIENT "Clustername"

 

Article URL http://www.symantec.com/docs/TECH42954

RamNagalla
Moderator
Moderator
Partner    VIP    Certified
16:08:34.598 [5308.6120] <8> CBatchDlg::OnInitDialog: WARN - Policy Dropdown not created: Server = NB Servername Client = SQL Node name
16:08:34.598 [5308.6120] <1> CBatchDlg::OnInitDialog:     CONTINUATION: - The system cannot find the path specified.
16:08:45.946 [3052.1964] <16> serverResponse: ERR - server exited with status 239: the specified client does not exist in the specified policy
 
what is the names associated with the IP address
192.168.150.14
192.168.150.9
one should be the client IP , resolve the IP to name and use the same to client Policy.

Katiebee
Level 4
Hi all, thanks for all the responses. The script contained the name of the SQL cluster so I have added the line BROWSECLIENT "Nodename" Re the policy for the backup, I have tried a variety of combinations of having the cluster name, the cluster name and node names, and just the node names. At the moment it has the DB Clustername and the node names. I am running the DB backup as I type but when it fails it does so quite quickly so I should be able to let you know soon if adding the node name to the script worked Many thanks again, Katie

Katiebee
Level 4
Thank you all, The issue was that the node name needed to be in the scripts as well, when I added to one script then ran it, the backup completed Hope you all have a good Christmas and New Year, Katie