backup sql server error status 25 cannot connect on socket(25)

[soway]

Dear all
i use veritas version 6.0 MP4 backup sql server
and policy type choose MS-SQL-Server

but also occure error status 25 cannot connect on socket(25)
i show all info from veritas log and sql server log
hope somebody can help me solve this problem, Thanks very much

--------veritas server side log--------
2007/8/17 上午 09:00:05 - requesting resource Tabkps02-Disk
2007/8/17 上午 09:00:05 - requesting resource tabkps02.NBU_CLIENT.MAXJOBS.TAESPS03
2007/8/17 上午 09:00:05 - requesting resource tabkps02.NBU_POLICY.MAXJOBS.TAESPS03-DB-Full
2007/8/17 上午 09:00:07 - Error bpbrm(pid=5956) cannot open progress file /C/Program?Files/VERITAS/NetBackup/Logs/user_ops/dbext/logs/2492.0.1187312403 on client TAESPS03    
2007/8/17 上午 09:00:07 - Error bpbrm(pid=5956) client open errno = 22       
2007/8/17 上午 09:00:07 - Error bpbrm(pid=5956) listen for client protocol error - couldn't write necessary information on /C/Program?Files/VERITAS/NetBackup/Logs/user_ops/dbext/logs/2492.0.1187312403
2007/8/17 上午 09:00:06 - granted resource tabkps02.NBU_CLIENT.MAXJOBS.TAESPS03
2007/8/17 上午 09:00:06 - granted resource tabkps02.NBU_POLICY.MAXJOBS.TAESPS03-DB-Full
2007/8/17 上午 09:00:06 - granted resource Tabkps02-Disk
2007/8/17 上午 09:00:06 - started process bpbrm (5956)
2007/8/17 上午 09:00:06 - connecting
2007/8/17 上午 09:00:07 - end writing
cannot connect on socket(25)

--------veritas client side log--------
Microsoft SQL Server  2000 - 8.00.2039 (Intel X86)
May  3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Batch = C:\SQLBackup_Full.bch, Op# = 13
INF - Using backup image taesps03.MSSQL7.TAESPS03.db.SPS01_Config_db.~.7.001of001.20070817090042..C
INF - backup database "SPS01_Config_db" to VIRTUAL_DEVICE='VNBU0-3232-1592-1187312442' with blocksize = 65536, maxtransfersize = 65536, buffercount = 1
INF - Number of stripes: 1, Number of buffers per stripe 1.
INF - Created VDI object for SQL Server instance <TAESPS03>. Connection timeout is <300> seconds.
09:00:54.729 [3232.4088] <4> : 09:00:48 INF - Server status = 25
ERR - Error in VxBSACreateObject: 3.
   CONTINUATION: - System detected error, operation aborted.
ERR - Error in VDS->Close: 0x80770004.
   CONTINUATION: - An abort request is preventing anything except termination actions.
INF - OPERATION #13 of batch C:\SQLBackup_Full.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 17(0) seconds.
INF - Results of executing <C:\SQLBackup_Full.bch>:

--------sql server log--------
BackupMedium::ReportIoError:  write 失敗 (於備份裝置 'VNBU0-3232-1592-1187312442')。作業系統錯誤 995(因為執行緒結束或應用程式要求，所以已中止 I/O 操作。)。

BACKUP 無法完成命令 backup database "SPS01_Config_db" to VIRTUAL_DEVICE='VNBU0-3232-1592-1187312442' with blocksize = 65536, maxtransfersize = 65536, buffercount = 1

Internal I/O request 0x75049C38: Op: Write, pBuffer: 0x0B940000, Size: 65536, Position: 0, UMS: Internal: 0x0, InternalHigh: 0x0, Offset: 0x0, OffsetHigh: 0x0, m_buf: 0x00000000, m_len: 0, m_actualBytes: 0, m_errcode: 995, BackupFile: VNBU0-3232-1592-1187312442

BackupVirtualDeviceFile::RequestDurableMedia:  Flush 失敗 (於備份裝置 'VNBU0-3232-1592-1187312442')。作業系統錯誤 995(因為執行緒結束或應用程式要求，所以已中止 I/O 操作。)。

[sdo]

Does a normal file system backup work?  i.e. try a backup of just one small folder, does this work?

Also, bperror can be used to supply a list of recommended actions:

$ bperror -S 25 -r

...also I noticed:

Error bpbrm(pid=5956) client open errno = 22 

...quite early in the log, but what isn't clear is whether this is a NetBackup error code 22 or possibly a Win32 error code.

Maybe this will help too:

$ bperror -S 22 -r

I might be misleading you, so take this with a pinch of salt, but Win32 error codes can be found here:

http://help.netop.com/support/errorcodes/win32_error_codes.htm

...and Windows error 22 is "the device does not recognize the command", which looks like a low level hardware request failure.

Can you supply a bit of background to the client and how the policy is configured, and what kind of storage you are attempting to save to?

[soway]

Dear sir

thank you very much of your reply

about my policy is use MS-SQL-Server and storage use disk array to save backup img

can you teach me where can be use recommended actions about ?

$ bperror -S 25 -r

$ bperror -S 22 -r

i'm not understand of this,thanks!!

[Omar_Villa]

Connection timeout is <300> seconds.

================================================

For what I see in the logs you are expiriencint time outs, Im sure your DB is to big and you need to increase your client timeout parameter, try it with 7200, is to must regular way for SQL backups and restores.

Hope this helps.

Regards

[Omar_Villa]

Also I saw some japanese simbols on your logs, dont know what those means.

[Chris_Sayles]

I am too having the same error. I changed the client read timeouts to 1800 seconds. The client connect timeout is set to 900 seconds on the master server. But the log still reports connection timeout of 300 seconds. Where should I be looking to change the timeout value?

Copyright (c) 1988-2003 Microsoft Corporation

Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

Batch = C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\alldbases.bch, Op# = 8
01:59:42.613 [7552.8108] <4> InitPipeInfo: INF - Using backup image ctmom01.MSSQL7.CTMOM01.db.ReportServerTempDB.~.7.001of001.20071002015942..C
01:59:42.613 [7552.8108] <4> Dbbackrec::CreateSQLcmdSyntax: INF - backup database "ReportServerTempDB" to VIRTUAL_DEVICE='VNBU0-7552-8108-1191286782' with blocksize = 65536, maxtransfersize = 65536, buffercount = 1
01:59:42.613 [7552.8108] <4> Dbbackrec::CreateSQLcmdSyntax: INF - Number of stripes: 1, Number of buffers per stripe 1.
01:59:42.613 [7552.8108] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_7552_4960>, SQL userid <sa> handle <0x01111a20>.
01:59:42.613 [7552.8108] <4> CDBbackrec::InitDeviceSet(): INF - Created VDI object for SQL Server instance <CTMOM01>. Connection timeout is <300> seconds.
01:59:44.457 [7552.5272] <2> vnet_vnetd_service_socket: ..\libvlibs\vnet_vnetd.c.2029: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
01:59:44.457 [7552.5272] <2> vnet_vnetd_service_socket: ..\libvlibs\vnet_vnetd.c.2043: service: bprd
01:59:44.972 [7552.5272] <2> logconnections: BPRD CONNECT FROM 172.17.1.14.3778 TO 172.19.250.14.13724
01:59:46.847 [7552.5272] <2> vnet_vnetd_service_socket: ..\libvlibs\vnet_vnetd.c.2029: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
01:59:46.847 [7552.5272] <2> vnet_vnetd_service_socket: ..\libvlibs\vnet_vnetd.c.2043: service: bprd
01:59:46.988 [7552.5272] <2> logconnections: BPRD CONNECT FROM 172.17.1.14.3779 TO 172.19.250.14.13724
02:04:56.988 [7552.5272] <16> serverResponse: ERR - server exited with status 25: cannot connect on socket
02:04:56.988 [7552.5272] <16> CreateNewImage: ERR - serverResponse() failed
02:04:56.988 [7552.5272] <16> VxBSACreateObject: ERR - Could not create new image with file /ctmom01.MSSQL7.CTMOM01.db.ReportServerTempDB.~.7.001of001.20071002015942..C.
02:04:56.988 [7552.5272] <4> getServerName: Read server name from nb_master_config: lynxbkup.netbackup.lynxtec.net
02:04:58.597 [7552.5272] <2> vnet_vnetd_service_socket: ..\libvlibs\vnet_vnetd.c.2029: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
02:04:58.597 [7552.5272] <2> vnet_vnetd_service_socket: ..\libvlibs\vnet_vnetd.c.2043: service: bprd
02:04:58.738 [7552.5272] <2> logconnections: BPRD CONNECT FROM 172.17.1.14.3880 TO 172.19.250.14.13724
02:05:17.847 [7552.5272] <16> DBBACKMAIN::WriteFailuresToServer: ERR - Internal error. See the dbclient log for more information.
02:05:17.847 [7552.5272] <32> DBBACKMAIN::WriteFailuresToServer: ERR - Status returned from dbc_RemoteWriteFile. AppStatus = <0>, WriteStatus = <25>
02:05:17.847 [7552.5272] <16> DBthreads::dbclient: ERR - Error in VxBSACreateObject: 3.
02:05:17.847 [7552.5272] <1> DBthreads::dbclient:     CONTINUATION: - System detected error, operation aborted.
02:05:17.847 [7552.5272] <8> close_image: Session being terminated abnormally, cleaning up
02:05:17.847 [7552.5272] <4> close_image: INF - backup FAILED
02:05:17.847 [7552.5272] <4> close_image: INF ---- end of Backup ---

Regards,

Chris

[IPE]

Hi Soway,

I'm having exactly the same error that you had with NetBackup 6.0 MP4 and SQL agent. In my case if I change the vnetd port to bpcd in the SQL client, the backup works correctly... Could you please let me know how did you solve the problem?

Regards,

IPE