SQL Server 2008 Developer SQL Server 2008 Enterprise SQL Server 2008 Express SQL Server 2008 R2 Developer SQL Server 2008 R2 Enterprise SQL Server 2008 R2 Express More…Less
Microsoft distributes Microsoft SQL Server 2008 Service Pack 1 (SP1) or SQL 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 SP1 or SQL 2008 R2 fix release.
Symptoms
Assume that an application tries to use Virtual Backup Device Interface (VDI) to back up some data in a Microsoft SQL Server 2008 or SQL Server 2008 R2 instance. In this situation, the application may stop responding and you may be unable to cancel the backup operation. Additionally, an error message that resembles the following may be logged in the SQL Server error log:
<Date Time> spid<n> Error: 18210, Severity: 16, State: 1.
<Date Time> spid<n> BackupMedium::ReportIoError: write failure on backup device ‘HotSrc’. Operating system error 39(The disk is full.).
Internal I/O request 0x0000000083A97CD0: Op: Write, pBuffer: 0x0000000000DA0200, Size: 512, Position: 0, SOS: Internal: 0x0, InternalHigh: 0x0, Offset: 0x0, OffsetHigh: 0x0, m_buf: 0x0000000000DA0200, m_len: 512, m_actualBytes: 0, m_errcode: 39, BackupFile: HotSrc
Cause
This issue occurs because the application expects VDI to send a command to close the VDI connection when the backup operation is complete. However, VDI does not send the command as expected.
Resolution
Cumulative update information
SQL Server 2008 Service Pack 2
The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2527180 Cumulative update package 4 for SQL Server 2008 Service Pack 2Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
The fix for this issue was first released in Cumulative Update 13. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 1 (SP1), click the following article number to view the article in the Microsoft Knowledge Base:
2497673 Cumulative update package 13 for SQL Server 2008 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 Service Pack 1 (SP1) fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
SQL Server 2008 R2 Service Pack 1
The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2544793 Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released
SQL Server 2008 R2
The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2507770 Cumulative Update package 7 for SQL Server 2008 R2 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
More Information
The following table provides more information about the products or tools that automatically check for this condition in your instance of SQL Server and in the versions of SQL Server against which the rule is evaluated.
|
Rule software |
Rule title |
Rule description |
Product versions against which the rule is evaluated |
|
System Center Advisor |
SQL Server can hang when you try to perform snapshot based Backup/Restore |
In this SQL Server instance advisor detected the presence of snapshot backup and the absence of a fix which might result in SQL Server hung state. Update the affected instance of SQL Server with the required fixe or avoid the SQL Server hang issue. |
SQL Server 2008 SQL Server 2008 R2 |
Need more help?
- Remove From My Forums
-
Вопрос
-
We are getting below error while running red gate backup.
BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device ‘SQLBACKUP_******’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.)
I am not getting any clue to resolve this error.
Ответы
-
We are getting below error while running red gate backup.
Then I would suggest to contact the support of RedGate, they may already know the issue:
www.red-gate.com/supportcenter/
Olaf Helper
[ Blog] [ Xing] [ MVP]
-
Предложено в качестве ответа
20 апреля 2015 г. 7:17
-
Помечено в качестве ответа
Lydia ZhangMicrosoft contingent staff
27 апреля 2015 г. 8:57
-
Предложено в качестве ответа
-
Hello,
Try to reduce the actual values on the following backup parameters as a workaround: max transfer size and limit the number
of threads.Monitor memory consumption on that server, this may be a possible cause.
Make sure the backup destination is not full.
Examine SQL Server error log and look for error messages prior in time to the one you posted.
Provide the logs created by this backup tool to RedGate Support.
Hope this helps.Regards,
Alberto Morillo
SQLCoffee.com
-
Изменено
Alberto MorilloMVP
17 апреля 2015 г. 15:22 -
Предложено в качестве ответа
PradyothanaDP
18 апреля 2015 г. 4:57 -
Помечено в качестве ответа
Lydia ZhangMicrosoft contingent staff
27 апреля 2015 г. 8:57
-
Изменено
- Remove From My Forums
-
Question
-
Issue :
===================
The backup job fails and I get Error: 18210, Severity: 16, State: 1. and Backup Error: 3041, Severity: 16, State: 1. in SQL Server ERRORLOG.
Error comes while taking full backup on SQL Server 2005 sp3.
ERRORLOG extract
===================
2009-11-28 01:13:01.920 spid62 Error: 18210, Severity: 16, State: 1.
2009-11-28 01:13:01.920 spid62 BackupMedium::ReportIoError: write failure on backup device ‘D:datadata_srvdbagroupdbamaintLDNTSY01SDPRddumpstmp_BackupSql_LDNTSY01SDPR_TRIPL_20091128_010512.BAK’. Operating system error 112(error not found).
2009-11-28 01:13:01.920 Backup Error: 3041, Severity: 16, State: 1.
2009-11-28
Application Log:
BackupMedium::ReportIoError: write failure on backup device ‘D:datadata_srvdbagroupdbamaintLDNTSY01SDPRddumpstmp_BackupSql_LDNTSY01SDPR_TRIPL_20091129_010214.BAK’. Operating system error 112(error not found).
Answers
-
Resolution
===================
Operating system error 112 is key message over here and suggests insufficient disk space. On looking at the backup drive which in this case is D drive, I saw the same issue i.e only few KBs were left . After cleaning up old backup files I re run the backup job and it succeeded.
I feel that SQL server message should have been simplified and more intuitive rather than with multiple confusing Error numbers
.
-
Marked as answer by
Sunday, November 29, 2009 3:08 AM
-
Marked as answer by
SQL Server is a powerful database management system that is used by many companies worldwide. Unfortunately, this system can suffer from backup issues which can lead to serious data loss. This article outlines the most common backup issues seen in SQL Server and how to prevent them.
Backup issues are a common problem when working with SQL Server. Below are some of the most frequent problems that may arise:
1. Insufficient disk space: Running out of disk space is one of the most common issues with SQL Server backup operations. It’s important to ensure that there is enough free disk space to store the backup files.
2. Permission issues: Having insufficient permissions can cause backup operations to fail. All users should have the necessary permissions to perform the backups, as well as access to the backup location.
3. Improper backup configuration: SQL Server backups should be configured correctly in order to ensure that they are successful. This includes configuring the backup file name, compression, and recovery model.
You can find here some of the frequent or common errors faced when manually performing a database backup or an automated maintenance plan or custom backup job failed.
Error: 3041, Severity: 16, State: 1
Backup failed to complete the command BACKUP DATABASE database_name. Check the backup application log for detailed messages.
Backup Error 3041 is a generic error that is returned when a backup fails. Along with this error, there are additional errors returned and can be found in the SQL Server error log. Look for other specific backup errors, which will point the cause of the backup failure.
Error: 18204, Severity: 16, State: 1
BackupDiskFile::CreateMedia: Backup device ‘\BackupServerBackupsTestTest_Backup.bak’ failed to create. Operating system error 53(the network path was not found.)
If you carefully read the complete error message, it gives the cause of the failure “Operating system error 53(the network path was not found”.
- Test If you are able to browse to this backup share \BackupServerBackupsTest. You need to test using the same account which is performing the backup, meaning if backups are running from SQL Server job, use the SQL Server and Agent service accounts to test access to the backup share.
- If this is happening intermittently, then possibly it was is network glitch, so work with your network administrator to run a network trace to identify network issues.
Msg 3201, Level 16, State 1, Line 1
Cannot open backup device ‘D:BackupsTest_backup.bak’. Operating system error 3(The system cannot find the path specified.)
Make sure that the path D:Backups exists, sometimes with user oversight, the path mentioned could be wrong lie the folder name could be backup and we use backups and will result in an error. – Another issue when this can occur is if there is any space at the end of the folder name.
Msg 3201, Level 16, State 1, Line 1
Cannot open backup device ‘D:BackupsAdv.bak’. Operating system error 5(Access is denied.)
- The above error occurred, because of permission issues on the backup folder. Grant Full Control on backup folder to SQL Server service account and to the account with which are you are trying to perform the backups.
- Also, make sure that the account used to perform backup has sufficient permissions to perform backups in SQL Server.
Error: 3043, Severity: 16, State: 1
BACKUP ‘Test_DB’ detected an error on page (1:12534) in file ’Test_DB.mdf’.
Error: 3043, Severity: 16, State: 1.
- The error 3043 occurs, if there is some sort of corruption in the database, which would again be mostly because if underlying hardware issues.
- Troubleshoot this issue in the direction, by first troubleshooting and fixing the database corruption issue.
Error: 18210, Severity: 16, State: 1
BackupMedium::ReportIoError: write failure on backup device ‘0a158c7d-a7a3-4d5a-8b58-124602e40a14’.
Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.)
- Error 18210 occurs mostly when a third-party backup tool is performing the backups of SQL databases using native T-SQL commands or by backing up the .mdf and .ldf files. Third-party tools generally use VDI/VSS and use VSSWriter or SQLWriter for performing the backups. Check for any problems with these writers.
- If you are not using any third-party tool for performing SQL database backups, then you can try disabling the OS and SQL VSS writer to see if backup completes successfully after disabling them.
- Check for any known issues with SQL Server or OS.
- Check for any known issues with the third backup software.
Msg 3009, Level 16, State 1, Line 1
Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful.
Whenever SQL Server database backup is performed, an entry for that backup is made into msdb..backupset table. Check if the data and log files of msdb is set for autogrowth. Verify if there is sufficient free space of the disk drive where msdb files are located.
Msg 3033, Level 16, State 0, Line 1
BACKUP DATABASE cannot be used on a database opened in emergency mode.
This error can occur if you try to perform backup of a database which is in emergency mode, which is not supported. Bring your database online and then perform the backups.
Msg 4208, Level 16, State 1, Line 1
The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
This error can occur, if we try to perform transaction log backup of a database whose recovery model is set to “SIMPLE”. Transaction Log backups are not supported for databases in Simple recovery mode. If the database is critical and recovering as much data is required and if point in time recovery is important, then change the recovery model of the database to “FULL” and then schedule job to perform regular transaction log backups.
SQL Server Backups causing operating system returned error 1450
The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00000000003200 in file with handle 0x0000101C. This is usually a temporary condition and the SQL Server will keep retrying the operation. If the condition persists then immediate action must be taken to correct it.
- Error 1450 is not related to SQL Server, it is related to Hardware/Operating System, so check for any configuration issues and make changes accordingly.
- Remove /3 GB switch if enabled, and try performing the backups.
- Make sure there is no corruption with database.
- Check for any issues with disk subsystem.
Msg 3241, Level 16, State 7, Line 1 & Msg 3013, Level 16, State 1, Line 1
Msg 3241, Level 16, State 7, Line 1
The media family on device ‘PathToBackupFileBackupFile.bak’ is incorrectly formed. SQL Server cannot process this media family.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
This issue can occur for various reasons, some of them are as mentioned below.
- Make sure the backup file is located on the same server where you are trying to restore. Check if the backup file is not corrupted. Try to move the backup file on to another drive or to another server and see if that works. Run below command to make sure there is no corruption with the backup file.
|
Restore verifyonly from disk = ‘PathToBackupFileBackupFile.bak’ |
- This error can also occur if you are trying to restore a database from lower version to higher version. Example, if you are trying to perform a restore from SQL Server 2012 database on SQL Server 2008 R2 instance. This scenario is not supported and cannot do it, so you have to script our all tables/SP’s/Views/Other objects from SQL 2012 and create them on SQL Server 2008 and then export the data from SQL Server 2012 to SQL Server 2008 R2
Hello,
I have maintenance plan for full database backup at 1:00 AM every day. I am getting following error message.
Do you have any idea about that?
Message
BACKUP failed to complete the command BACKUP DATABASE lansweeperdb. Check the backup application log for detailed messages.
Message
Error: 3041, Severity: 16, State: 1.
Message
BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}1’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
Message
Error: 18210, Severity: 16, State: 1.
Please help me out for this. I am also attaching screenshot from eventviewer.
I have also checked my application log and I found following:
2018-02-28 01:01:16.01 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.01 Backup BACKUP failed to complete the command BACKUP DATABASE lansweeperdb. Check the backup application log for detailed messages.
2018-02-28 01:01:16.17 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BACKUP failed to complete the command BACKUP DATABASE model. Check the backup application log for detailed messages.
2018-02-28 01:01:16.17 spid77 Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.17 spid77 BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}1’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.17 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BACKUP failed to complete the command BACKUP DATABASE msdb. Check the backup application log for detailed messages.
2018-02-28 01:01:16.17 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}2’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.17 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}3’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.17 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BACKUP failed to complete the command BACKUP DATABASE TmsEPrd. Check the backup application log for detailed messages.
2018-02-28 01:01:16.17 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BACKUP failed to complete the command BACKUP DATABASE TmsEPly. Check the backup application log for detailed messages.
2018-02-28 01:01:16.17 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}4’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.17 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BACKUP failed to complete the command BACKUP DATABASE TmsEIM. Check the backup application log for detailed messages.
2018-02-28 01:01:16.17 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BACKUP failed to complete the command BACKUP DATABASE ICS_NET. Check the backup application log for detailed messages.
2018-02-28 01:01:16.17 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}5’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.17 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BACKUP failed to complete the command BACKUP DATABASE PowerFAIDS_Production. Check the backup application log for detailed messages.
2018-02-28 01:01:16.17 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}6’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.17 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BACKUP failed to complete the command BACKUP DATABASE ICS_NET_STAT. Check the backup application log for detailed messages.
2018-02-28 01:01:16.17 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}7’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.17 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}8’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.17 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BACKUP failed to complete the command BACKUP DATABASE Mesalands_Conversion. Check the backup application log for detailed messages.
2018-02-28 01:01:16.17 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}10’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.17 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BACKUP failed to complete the command BACKUP DATABASE PowerFAIDS_Test. Check the backup application log for detailed messages.
2018-02-28 01:01:16.17 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}9’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.17 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BACKUP failed to complete the command BACKUP DATABASE TmsEJICSTest. Check the backup application log for detailed messages.
2018-02-28 01:01:16.17 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.17 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}11’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.18 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BACKUP failed to complete the command BACKUP DATABASE ICS_NET_TEST. Check the backup application log for detailed messages.
2018-02-28 01:01:16.18 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}16’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.18 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BACKUP failed to complete the command BACKUP DATABASE ICS_NET_STAT_DROP. Check the backup application log for detailed messages.
2018-02-28 01:01:16.18 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BACKUP failed to complete the command BACKUP DATABASE EQCAS. Check the backup application log for detailed messages.
2018-02-28 01:01:16.18 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}17’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.18 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BACKUP failed to complete the command BACKUP DATABASE ICS_NET_STAT_TEST. Check the backup application log for detailed messages.
2018-02-28 01:01:16.18 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BACKUP failed to complete the command BACKUP DATABASE MCN_Save_083012. Check the backup application log for detailed messages.
2018-02-28 01:01:16.18 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BACKUP failed to complete the command BACKUP DATABASE MCN_Sonisweb. Check the backup application log for detailed messages.
2018-02-28 01:01:16.18 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}19’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.18 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BACKUP failed to complete the command BACKUP DATABASE mcn_xlate. Check the backup application log for detailed messages.
2018-02-28 01:01:16.18 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BACKUP failed to complete the command BACKUP DATABASE ICS_NET_DROP. Check the backup application log for detailed messages.
2018-02-28 01:01:16.18 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}12’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.18 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}13’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.18 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}18’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.18 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}15’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.18 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}14’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.18 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BACKUP failed to complete the command BACKUP DATABASE avast_sbc_db. Check the backup application log for detailed messages.
2018-02-28 01:01:16.18 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}21’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.18 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BACKUP failed to complete the command BACKUP DATABASE Ultrasound. Check the backup application log for detailed messages.
2018-02-28 01:01:16.18 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}22’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.18 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BACKUP failed to complete the command BACKUP DATABASE Report_ServerTempDB. Check the backup application log for detailed messages.
2018-02-28 01:01:16.18 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}24’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.18 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BACKUP failed to complete the command BACKUP DATABASE Report_Server. Check the backup application log for detailed messages.
2018-02-28 01:01:16.18 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}23’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.18 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BACKUP failed to complete the command BACKUP DATABASE TmsEIzendaTest. Check the backup application log for detailed messages.
2018-02-28 01:01:16.18 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.18 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}25’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:01:16.19 Backup Error: 3041, Severity: 16, State: 1.
2018-02-28 01:01:16.19 Backup BACKUP failed to complete the command BACKUP DATABASE master. Check the backup application log for detailed messages.
2018-02-28 01:01:16.19 Backup Error: 18210, Severity: 16, State: 1.
2018-02-28 01:01:16.19 Backup BackupIoRequest::ReportIoError: write failure on backup device ‘{555F656D-2E82-4EDE-AE3B-DF3B98F5DF33}26’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2018-02-28 01:02:23.68 Backup Database backed up. Database: lansweeperdb, creation date(time): 2013/05/22(15:51:22), pages dumped: 1077559, first LSN: 10556359:4177:278, last LSN: 10556360:359:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {‘D:SQL Backupslansweeperdblansweeperdb_backup_2018_02_28_010002_0930862.bak’}). This is an informational message only. No user action is required.
2018-02-28 01:02:23.72 Backup BACKUP DATABASE successfully processed 1077497 pages in 80.847 seconds (104.121 MB/sec).
2018-02-28 01:02:43.23 Backup Database backed up. Database: PowerFAIDS_Production, creation date(time): 2012/04/13(14:07:02), pages dumped: 20491, first LSN: 30678:479:38, last LSN: 30678:497:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {‘D:SQL BackupsPowerFAIDS_ProductionPowerFAIDS_Production_backup_2018_02_28_010002_3241001.bak’}). This is an informational message only. No user action is required.
2018-02-28 01:02:43.31 Backup BACKUP DATABASE successfully processed 20474 pages in 1.538 seconds (103.996 MB/sec).
2018-02-28 01:04:55.62 Backup Database backed up. Database: TmsEPrd, creation date(time): 2012/04/09(08:37:38), pages dumped: 2171951, first LSN: 493745:1750279:148, last LSN: 493745:1750415:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {‘D:SQL BackupsTmsEPrdTmsEPrd_backup_2018_02_28_010002_3701025.bak’}). This is an informational message only. No user action is required.
Thanks
Hi Paul
here is the info on the sql server from 1-12-13
I am using SSMS maint plans to back up databases right now
Does that use vss writer service ?
I looked at the info on the url and that pertains to vss writer so that is why
I am asking the above question.
I see this type of error in my logs which is similar to the (Error messages) in the url:
2013-01-12 10:06:28.41 spid94 Error: 18210, Severity: 16, State: 1.
2013-01-12 10:06:28.41 spid94 BackupMedium::ReportIoError: write failure on
backup device ‘0a158c7d-a7a3-4d5a-8b58-124602e40a14’.
Operating system error 995(The I/O operation has been
aborted because of either a thread exit or an application
request.).
2013-01-12 10:06:28.52 spid94 Error: 18210, Severity: 16, State: 1.
2013-01-12 10:06:28.52 spid94 BackupVirtualDeviceFile::RequestDurableMedia:
Flush failure on backup device ‘0a158c7d-a7a3-4d5a-8b58-
124602e40a14′.
Operating system error 995(The I/O operation has been aborted
because of either a thread exit or an application request.).
SQL Server and Resource Database Version
—————————————-
Microsoft SQL Server 2005 — 9.00.5069.00 (X64)
Aug 22 2012 18:02:46
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition (64-bit)
Windows NT 5.2 (Build 3790: Service Pack 2)
Edition/ProductVersion/ProductLevel/ResourceLastUpdateDateTime
—————————————————————
Developer Edition (64-bit)
9.00.5069.00
SP4
Aug 22 2012 4:59PM
What are your thoughts ?
Thanks
Jim
Last week i was busy with sorting out the optimal backup parameters for a server with large databases on Azure VM. Some backups were around 1 TB with compression enabled.
I used Ola hallengren’s backup script for backup plan implementation. It supports the backup on Azure blob storage.
Reducing the MaxTransferSize
During the research activity i tried MaxTransferSize = 65536. It is minimum value that can be used with this parameter. I was interested to minimize the resources used by backup process even if take longer to complete. That is why i tested 65536 bytes instead of 4194304 (4 MB) i.e max value for this option. (It did not work for purpose)
Error Message
Surprisingly backup failed within some time with following error message
Write on “https://%.bak” failed: 1117(The request could not be performed because of an I/O device error.)
I further checked the SQL Server logs and found following more specific error message
Error: 18210, Severity: 16, State: 1.
Write to backup block blob device https://% failed. Device has reached its limit of allowed blocks.
Blocks count constraint
This was in connection with maxtransfersize value that i just changed to its minimum. Checked more resources on blob storage and came to know an important fact. i.e.
A block blob storage can go up to 50000 blocks. You can use 64 KB to 4 MB of each of these blocks. Obviously blocks of 4 MB will hold more backup pages than of 64 KB blocks.
As i used small size blocks through maxtransfersize parameter then 50000 blocks on backup device consumed soon and error message was generated.
Combining maxtransfersize and block count
SQL Server version 2016 onwards is using API capable of using block blob storage as backup device and can hold backup size around 195 GB. And if backup size is bigger then it can be striped further in max 195 GB each. But important thing is to keep in mind is that 195 GB device size is only true for 4 MB maxtransfersize ( 4194304 bytes).
Formula
Following formula will help to estimate that how large your backup device strip may be with a certain maxtransfersize value.
maxtransfersize * 500000 = Backup device strip size (Bytes)
For example with maxtransfersize 65536 we will have a backup device strip of 65536 * 50000 = 3.05 GB.
Similarly for maxtransfersize 4194304 we will have full capacity of backup device strip 4194304 * 50000 = 195.31 GB
Same is the case with other multiples of 65536 that is min value of maxtransfersize parameter.
Conclusion
Use above mentioned formula to decide the number of backup strips to accommodate your backup. Backup strips may be up to 64 that is quite good size to manage large compressed backups. 64 * 195.31 = 12500 GB (12.2 TB).
Backup and restore operations even though they are supposed to be a no-brainer, it can leave you wanting to tear your hair out. Considering the different elements that influence the outcome of a successful backup operation like backup media, consistency of the backup, network issues (if backing up to a UNC path), consistency of the database being backed up etc.
I shall attempt to outline a set of troubleshooting steps specifically for non-native backup/restore related errors for SQL Server databases.
Any BACKUP command that completes successfully or with errors has associated messages logged in the SQL Server Errorlog.
A successful backup from the SQL Server Errorlog:
Database backed up. Database: adventureworks, creation date(time): 2010/05/28(03:00:18), pages dumped: 17291, first LSN: 67:7733:56, last LSN: 67:7761:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {‘F:adventureworks.bak’}).
You will see that the backup completion message has the database name, the number of pages that were contained in the backup, the date the backup was created and the number of devices and their type (in this case files). So you can reconstruct the sequence of backups even if your backup information history is missing from the MSDB system tables and you just have your SQL Server Errorlogs to play with. If you want to get real fancy about this, then you could spin up a nifty little Powershell or VBScript to parse through the SQL Errorlogs and provide the backup sequence to you as well.
Now, let’s look at a failed backup message from the SQL Errorlog.
Error: 18204, Severity: 16, State: 1.
BackupDiskFile::CreateMedia: Backup device ‘R:adventureworks.bak’ failed to create. Operating system error 3(The system cannot find the path specified.).
Error: 3041, Severity: 16, State: 1.
BACKUP failed to complete the command BACKUP DATABASE adventureworks.
You will notice above that the Operating System error code associated with the backup failure is reported in the error message. More often than not, the error message is self explanatory. If the error code doesn’t throw back an error text along with it, you can get the windows error code associated with the error code using net helpmsg <error number> from a command prompt window.
In the above case, there wasn’t any R: drive on my server. Now that I have finished stating the most obvious of troubleshooting methodologies for SQL native backups which was done to set the context for the next part of this post. The troubleshooting methodology for non-native backups.
Non-native SQL backups of databases use one of the following methods:
1. Use of APIs exposed through SQLVDI.dll to perform a VDI based backup
2. Use of VSS framework to perform a snapshot backup of the SQL Server database
Note: In this post, I shall not be addressing any storage level backup solutions that have options or features to handles SQL database backups.
This post is aimed at discussing the tackling of VSS/VDI related errors that you face while performing a database backup.
If a VDI backup fails, then you can try the following sequence of troubleshooting steps:
1. Attempt a backup to the same location using native SQL backup from a query window or SQLCMD. This might not always be possible as some of the backup tools do not allow any other backup application to connect to the backup share apart from the backup tool’s agents.
2. The next thing that you can do is to ensure that your SQLVDI.DLL is updated to the latest build. For this you can use the SQL Server Backup Simulator available on Code Gallery using the “Validate VDI Installation” option in the tool. This check in the tool will perform basic checks like current DLL version and additional checks based on root causes of common scenarios that CSS has seen in the past for VDI backup failures. Additional information on the usage of the tool is available here.
3. Perform a backup of the database using the tool for which the backup is failing (to the same destination if possible). The parameter tweaks at this point are not available in the current version like striped backups, changes to MAXTRANSFERSIZE/BUFFER COUNT etc. but if the backup from this tool is successful, then you know for a fact that the SQLVDI APIs are working as expected. Then it is either an additional piece of logic in the backup software that is failing or there is an external factors like network/backup media or there is a resource crunch on the SQL instance on which the database resides.
Common errors that you might see during a VDI backup operation failure:
Error message 1
BackupVirtualDeviceFile::ClearError: 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 2
Error: 18210, Severity: 16, State: 1.
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 3
Error: 18210, Severity: 16, State: 1.
BackupVirtualDeviceFile::RequestDurableMedia: Flush 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.)
The above errors are mostly due to outdated versions of SQLVDI.DLL on SQL Server 2000 or SQL Server 2005 instances. The “Validate VDI Installation” option in the Backup Simulator should be able to identify any known issues with DLL version mismatch for you.
If you have an application that uses Volume Shadow Service to backup your SQL database and that backup fails, then you your troubleshooting steps would be a bit different. The tell-tale sign of a VSS Snapshot backup is in the I/O Frozen message being written into the SQL Errorlogs for the databases being backed up. In such a failure scenario, take a backup of the database using Windows Server Backup Admin (Windows Server 2008 and above) or NTBackup utility to perform a backup of the database files involved. If this backup is successful, it means that a snapshot backup is successfully completing for the database. Now depending on your backup application’s implementation logic, this might be a resource crunch or a backup storage media incompatibility or even a resource crunch.
Common errors associated with VSS backups:
Issue# 1
Error: 3041, Severity: 16, State: 1.
Backup BACKUP failed to complete the command BACKUP DATABASE <database name>. Check the backup application log for detailed messages.
SubprocessMgr::EnqueueSubprocess: Limit on ‘Max worker threads’ reached.
This error message is raised when your backup application uses VSS to backup a large number of databases simultaneously. More information around this can be found in this post Volume Shadow barfs with 0x80040e14 code
Issue #2
While performing a Bare Metal backup you might run into issues if your SQL Server binaries are located on a different drive other than the C: drive. More information on the same is mentioned here: Location of SQL Binaries can flip out Bare Metal backups
Issue #3
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 6005
Description:
Sqllib error: Database %1 is stored on multiple volumes, only some of which are being shadowed.
The above error occurs when you backup only one of the volumes that contains SQL database data/log files which are spread over multiple volumes. This is explained in detailed in this post: Why is VSS complaining about SQL Data files
More information on how VSS/VDI work is present in the blog post by Sudarshan: INFORMATIONAL- SHEDDING LIGHT on VSS & VDI Backups in SQL Server
Previous posts related to Volume Shadow Backups
IO Frozen messages while taking NT Backup for SQL databases
Previous posts related to VDI backups
SQL VDI backup fails with 0×80770007