cancel
Showing results for 
Search instead for 
Did you mean: 

SQL backup child streams failing in error code 25.

SaviN
Level 3
Partner
The aim to backup this client-a is via backup NIC (hostname-bk) and the backup jobs running for this is as follows:
 
OS flat-file - completing successfully.
SQL DB - child jobs are failing in error code 25.
 
I have uploaded the following logs for your reference:
detailed status of one child stream, bphdb, bpclient and bpbkar
 
Could you please help on this issue?
1 ACCEPTED SOLUTION

Accepted Solutions

sri_vani
Level 6
Partner

 may be due to a SQL Server virtual memory issue or limitation on the Windows client system.

 

please verify below two links:

http://support.microsoft.com/kb/934396

http://www.symantec.com/business/support/index?page=content&id=TECH77008

View solution in original post

6 REPLIES 6

RamNagalla
Moderator
Moderator
Partner    VIP    Certified
bphdb log:-
07:33:45.664 [11356.7880] <16> writeToSock: ERR - send() to server failed: An existing connection was forcibly closed by the remote host. 
07:33:45.664 [11356.7880] <16> bphdb.CreateProcessForNT: ERR - could not write keepalive to the NAME socket
07:33:45.664 [11356.7880] <16> bphdb.do_launch_ex: ERR - CreateProcessForXX exit status  :  (24)
07:33:45.664 [11356.7880] <4> bphdb.do_launch_ex: ERR - exit status  :  (24)
07:33:45.664 [11356
 
 
dbclient log:- 
 
00:13:29.531 [9516.8620] <16> ReadFromVirtualDevice: ERR - Error in GetCommand: 0x80770004
 
 
by any chance does it because of the reason specified in the below tech note
 

SaviN
Level 3
Partner

There are several SQL DB backup jobs are running through the NetBackup policy. I have attached the parent job's detailed status for reference.

Will_Restore
Level 6

Look to the Event Viewer on the SQL Server for clues.

 

SaviN
Level 3
Partner

I have lot of the following two errors in the event viewer.

Event Viewer log:

Log Name:      Application
Source:        SQLVDI
Date:          11/6/2013 8:17:40 AM
Event ID:      1
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1596. Thread=1280. Server. Instance=MSSQLSERVER. VD=Global\VNBU0-5116-6772-1383750156_SQLVDIMemoryName_0. 
 
 
Log Name:      Application
Source:        MSSQLSERVER
Date:          11/6/2013 8:17:40 AM
Event ID:      18210
Task Category: (2)
Level:         Error
Keywords:      Classic
User:          svc_prd_SQLServer
Computer:      xxxxxxx
Description:
BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'VNBU0-5116-6772-1383750156'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
 
 
 
VSS Writer Status:
 
 
C:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
 
Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error
 
Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error
 
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {bc59d9fd-dc80-4405-a1b3-df0dce56533c}
   State: [1] Stable
   Last error: No error
 
Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {c0f7b459-22fb-4acb-87e9-b2c67fcbf3d4}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {932932e0-853b-40ae-8214-e7f68fa305fd}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {1f96e8b9-9737-4f43-802a-1e75e3f4e66a}
   State: [1] Stable
   Last error: No error
 
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {5f30c68f-e300-42cb-a944-942e48a369e5}
   State: [5] Waiting for completion
   Last error: No error
 
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {f9429c38-831d-4d2a-b212-32d5b2cdfd99}
   State: [1] Stable
   Last error: No error
 
Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {82a7a876-ce28-4709-82f6-22a730ca36f6}
   State: [1] Stable
   Last error: No error
 

 

sri_vani
Level 6
Partner

 may be due to a SQL Server virtual memory issue or limitation on the Windows client system.

 

please verify below two links:

http://support.microsoft.com/kb/934396

http://www.symantec.com/business/support/index?page=content&id=TECH77008

SaviN
Level 3
Partner

The recommended hotfix has been applied and issue has been fixed. Thank you.