SQL Full Backup Issue

[rahul350]

Client netbackup 7.6.1.2
and master server 7.6.1.2
 
 
Hi All,

I am facing SQL backup issue for full backup below is the dbclient log. Please provide any solution.

Microsoft SQL Server 2008 R2 (SP2) - 10.50.4033.0 (X64)

Jul  9 2014 16:04:25

Copyright (c) Microsoft Corporation

Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)

Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\sqldbs_full.bch, Op# = 1
21:30:23.563 [1164.4728] <2> vnet_pbxConnect: pbxConnectEx Succeeded
21:30:23.564 [1164.4728] <2> logconnections: BPRD CONNECT FROM 172.30.131.31.58953 TO 172.30.131.22.1556 fd = 784
21:30:23.606 [1164.4728] <4> InitPipeInfo: INF - Using backup image GLSBWPRD01.MSSQL7.GLSBWPRD01.db.BP1.~.7.001of001.20150704213022..C
21:30:23.612 [1164.4728] <2> vnet_pbxConnect: pbxConnectEx Succeeded
21:30:23.613 [1164.4728] <2> logconnections: BPRD CONNECT FROM 172.30.131.31.58954 TO 172.30.131.22.1556 fd = 784
21:30:23.646 [1164.4728] <4> Dbbackrec::CreateSQLcmdSyntax: INF - backup database "BP1" to VIRTUAL_DEVICE='VNBU0-1164-4728-1436045423' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
21:30:23.659 [1164.4728] <2> vnet_pbxConnect: pbxConnectEx Succeeded
21:30:23.659 [1164.4728] <2> logconnections: BPRD CONNECT FROM 172.30.131.31.58955 TO 172.30.131.22.1556 fd = 796
21:30:23.678 [1164.4052] <2> vnet_pbxConnect: pbxConnectEx Succeeded
21:30:23.678 [1164.4052] <2> logconnections: BPRD CONNECT FROM 172.30.131.31.58956 TO 172.30.131.22.1556 fd = 836
21:30:23.702 [1164.4728] <4> Dbbackrec::CreateSQLcmdSyntax: INF - Number of stripes: 1, Number of buffers per stripe 2.
21:30:23.995 [1164.4728] <2> vnet_pbxConnect: pbxConnectEx Succeeded
21:30:23.995 [1164.4728] <2> logconnections: BPRD CONNECT FROM 172.30.131.31.58957 TO 172.30.131.22.1556 fd = 836
21:30:24.039 [1164.4728] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_1164_3144_3>, SQL userid <sa> handle <0x004abbe0>.
21:30:24.049 [1164.4728] <4> CDBbackrec::InitDeviceSet(): INF - Created VDI object for SQL Server instance <GLSBWPRD01>. Connection timeout is <300> seconds.
21:30:24.052 [1164.4728] <2> vnet_pbxConnect: pbxConnectEx Succeeded
21:30:24.052 [1164.4728] <2> logconnections: BPRD CONNECT FROM 172.30.131.31.58959 TO 172.30.131.22.1556 fd = 940
21:35:24.117 [1164.4728] <4> getServerName: Read server name from nb_master_config: gbstbck01.ag.ad.local
21:35:24.131 [1164.4728] <2> vnet_pbxConnect: pbxConnectEx Succeeded
21:35:24.132 [1164.4728] <2> logconnections: BPRD CONNECT FROM 172.30.131.31.58989 TO 172.30.131.22.1556 fd = 568
21:35:24.197 [1164.4728] <4> getServerName: Read server name from nb_master_config: gbstbck01.ag.ad.local
21:35:24.212 [1164.4728] <2> vnet_pbxConnect: pbxConnectEx Succeeded
21:35:24.212 [1164.4728] <2> logconnections: BPRD CONNECT FROM 172.30.131.31.58990 TO 172.30.131.22.1556 fd = 568
21:35:26.315 [1164.4728] <16> CDBbackrec::InitDeviceSet_Part2(): ERR - Error in GetConfiguration: 0x80770003.
21:35:26.328 [1164.4728] <2> vnet_pbxConnect: pbxConnectEx Succeeded
21:35:26.328 [1164.4728] <2> logconnections: BPRD CONNECT FROM 172.30.131.31.58993 TO 172.30.131.22.1556 fd = 568
21:35:26.365 [1164.4728] <1> CDBbackrec::InitDeviceSet_Part2():     CONTINUATION: - The api was waiting and the timeout interval had elapsed.
21:35:26.368 [1164.4728] <2> vnet_pbxConnect: pbxConnectEx Succeeded
21:35:26.368 [1164.4728] <2> logconnections: BPRD CONNECT FROM 172.30.131.31.58994 TO 172.30.131.22.1556 fd = 568
21:35:26.403 [1164.4728] <4> KillAllThreads: INF - Killing group #0
21:35:26.403 [1164.4728] <4> KillAllThreads: INF - Issuing SignalAbort to MS SQL Server VDI
21:35:26.403 [1164.5736] <4> KillAllThreads: INF - Killing group #0
21:35:26.410 [1164.3596] <4> KillAllThreads: INF - Killing group #0
21:35:26.415 [1164.4052] <4> KillAllThreads: INF - Killing group #0
21:35:29.416 [1164.4728] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x004abbe0>
21:35:29.416 [1164.4728] <4> getServerName: Read server name from nb_master_config: gbstbck01.ag.ad.local
21:35:29.427 [1164.4728] <2> vnet_pbxConnect: pbxConnectEx Succeeded
21:35:29.427 [1164.4728] <2> logconnections: BPRD CONNECT FROM 172.30.131.31.58995 TO 172.30.131.22.1556 fd = 824
21:35:31.530 [1164.4728] <4> Dbbackrec::Perform: INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\sqldbs_full.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 309(309) seconds.
21:35:31.548 [1164.4728] <2> vnet_pbxConnect: pbxConnectEx Succeeded
21:35:31.548 [1164.4728] <2> logconnections: BPRD CONNECT FROM 172.30.131.31.58998 TO 172.30.131.22.1556 fd = 824
21:35:33.587 [1164.3144] <4> CGlobalInformation::CreateDSN: INF - Using ODBC Driver <SQL Server>
21:35:33.596 [1164.3144] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_1164_3144_4>, SQL userid <sa> handle <0x0051c260>.
21:35:33.603 [1164.3144] <4> CGlobalInformation::CreateDSN: INF - A successful connection to SQL Server <GLSBWPRD01\> has been made using standard security with DSN <NBMSSQL_1164_3144_4>
21:35:33.603 [1164.3144] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x0051c260>
21:35:33.603 [1164.3144] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_1164_3144_4>, SQL userid <sa> handle <0x0051c260>.
21:35:33.608 [1164.3144] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x0051c260>
21:35:33.609 [1164.3144] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_1164_3144_4>, SQL userid <sa> handle <0x0051c260>.
21:35:33.614 [1164.3144] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x0051c260>
21:35:33.614 [1164.3144] <4> CDBbackcat::GetVirtualServer: INF - Accessing database instance <GLSBWPRD01> on server <GLSBWPRD01>.
21:35:33.626 [1164.3144] <2> vnet_pbxConnect: pbxConnectEx Succeeded
21:35:33.626 [1164.3144] <2> logconnections: BPRD CONNECT FROM 172.30.131.31.59002 TO 172.30.131.22.1556 fd = 760
21:35:33.877 [1164.3144] <2> vnet_pbxConnect: pbxConnectEx Succeeded
21:35:33.877 [1164.3144] <2> logconnections: BPRD CONNECT FROM 172.30.

[rahul350]

On Media Server both client connect timeout and client read timeout set to 1800 sec. Also on Cliet.

[a_la_carte]

Has this SQL full backup ever worked before?

What is the error code you are getting when the full backup eventually fails ? Error code 6 or something else ?

[Marianne]

INF - Created VDI object for SQL Server instance <GLSBWPRD01>. Connection timeout is <300> seconds.

The SQL VDI timeout is still set to 300 (5 min).

You can increase this timeout in the backup script. VDI timeout parameter is described in NBU for MS-SQL manual.

I do not have access to manuals right now, but you can download the NBU for MS-SQL manual from 'Handy NBU Links' in my signature . 

[rahul350]

Hi Marianne,

I have attached the Timeout of Master/media server client and backup script. Please check were i need to change the settings.

[Marianne]

p.37 of  NetBackup for Microsoft SQL Server Administrator's Guide  lists VDITIMEOUTSECONDS in the table.

To make this 1800 as well, add this line somewhere before ENDOPER TRUE:

VDITIMEOUTSECONDS 1800

[rahul350]

Hi Marianne,

One more thing we have daily backups also in which we also take full backup and it work fine but only on weekly backup which runs on saturday this error occurs but when we re-run the bcakup it completes successfuly. We use same script for Daily as well as weekly backup. Please advise.

[Marianne · Accepted solution]

You will need to ask the SQL dba that question. Bear in mind that SQL needs to read the data and send it to NBU. Find out what else is happening on a Saturday during NBU backup window. Check SQL error and VDI logs.

[rahul350]

Thanks for you help Marianne. Will check with DBA team.