SQL database backup failing with Flush or Write failure on backup device, Operating system error 995 (failed to retrieve text for this error. Reason: 15105)

SQL database backup failing with Flush or Write failure on backup device, Operating system error 995 (failed to retrieve text for this error. Reason: 15105)

  • Article ID:100009801
  • Last Published:
  • Product(s):NetBackup
  • Ratings: 4 3

Problem

 SQL database backup failing with Flush or Write failure on backup device, Operating system error 995 (failed to retrieve text for this error. Reason: 15105)

BackupMedium::ReportIoError: write failure on backup device 'VDI_DeviceID'. 
Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.) 

Error Message

 

Info dbclient(pid=2564) Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2) 
6/14/2013 9:06:23 AM - Info dbclient(pid=2564) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\Default.bch, Op# = 1 
6/14/2013 9:06:23 AM - Info dbclient(pid=2564) INF - Using backup image SQLSERVERINSTANCE.MSSQL7.SQLSERVERINSTANCE.db.database.~.7.001of001.20130614090646..C 
6/14/2013 9:06:24 AM - Info dbclient(pid=2564) INF - backup database "database" to VIRTUAL_DEVICE='VNBU0-2564-144-1371215207' with blocksize = 65536, maxtransfersize = 4194304, buffercount = 2 
6/14/2013 9:06:24 AM - Info dbclient(pid=2564) INF - Number of stripes: 1, Number of buffers per stripe 2. 
6/14/2013 9:06:24 AM - Info dbclient(pid=2564) INF - Created VDI object for SQL Server instance <NASSAU>. Connection timeout is <300> seconds. 
6/14/2013 9:11:26 AM - Info dbclient(pid=2564) ERR - Error in GetConfiguration: 0x80770003. 
6/14/2013 9:11:26 AM - Info dbclient(pid=2564) CONTINUATION: - The api was waiting and the timeout interval had elapsed. 
6/14/2013 9:11:31 AM - Info dbclient(pid=2564) ERR - Error in VDS->Close: 0x80770004. 
6/14/2013 9:11:31 AM - Info dbclient(pid=2564) CONTINUATION: - An abort request is preventing anything except termination actions. 
6/14/2013 9:11:31 AM - Info dbclient(pid=2564) INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\Default.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 309(309) seconds. 
6/14/2013 9:11:33 AM - Info dbclient(pid=2564) INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\Default.bch>: 
6/14/2013 9:11:33 AM - Info dbclient(pid=2564) <0> operations succeeded. <1> operations failed. 
6/14/2013 9:11:33 AM - Info dbclient(pid=2564) INF - The following object(s) were not backed up successfully. 
6/14/2013 9:11:34 AM - Info dbclient(pid=2564) INF - database 
6/14/2013 9:11:34 AM - Error bpbrm(pid=3216) from client sqlhost: ERR - command failed: none of the requested files were backed up (2) 
6/14/2013 9:11:34 AM - Error bpbrm(pid=3216) from client sqlhost: ERR - bphdb exit status = 2: none of the requested files were backed up 
6/14/2013 9:11:34 AM - Error bpbrm(pid=3216) cannot send mail to xxxxxxx
6/14/2013 9:11:35 AM - Info bphdb(pid=2668) done. status: 2: none of the requested files were backed up 
6/14/2013 9:11:35 AM - end writing 
none of the requested files were backed up(2)
Event Type: Error 
Event Source: MSSQLSERVER 
Event Category: (6) 
Event ID: 17055 
Date: 6/24/2013 
Time: 11:01:07 PM 
User: SQLSERVERinstance\Administrator 
Computer: SQLHOST 
Description: 
3041 : 
BACKUP failed to complete the command backup database "database" to VIRTUAL_DEVICE='VNBU0-6536-6620-1372128357' with blocksize = 65536, maxtransfersize = 4194304, buffercount = 2 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. 
Data: 
0000: e1 0b 00 00 10 00 00 00 á....... 
0008: 07 00 00 00 4e 00 41 00 ....S.Q. 
0010: 53 00 53 00 41 00 55 00 L.H.O.S. 
0018: 00 00 09 00 00 00 64 00 ......d. 
0020: 65 00 6c 00 74 00 65 00 a.t.a.b. 
0028: 6b 00 74 00 65 00 00 00 a.s.e... 
sql server 00 
SQL native backups would fail:
Event Type: Warning 
Event Source: SQLSERVERAGENT 
Event Category: Job Engine 
Event ID: 208 
Date: 6/13/2013 
Time: 3:02:04 AM 
User: N/A 
Computer: Instance 
Description: 
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB Maintenance Plan1'4' (0x11BF4C5A273FE849A3D9AC8BAF4B0E4E) - Status: Failed - Invoked on: 2013-06-13 03:00:00 - Message: The job failed. The Job was invoked by Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1). 

Cause

 Virtual memory limitation on the client system which sometimes is cleared up after reboot.

Solution

  If issue persists after reboot, engage Microsoft Support to further look at the SQL-VDI Flush failure errors reported by SQL Server.



Applies To

 SQL client running Windows 2008 R2, SQL 2008, SQL 2005

Related Articles

SQL transaction log failing with Flush failure on backup device, Operating system error 995 (failed to retrieve text for this error. Reason: 15105)

Was this content helpful?