Sql ошибка 3041 серьезность 16 состояние 1

Проблема:  Иногда при ночном создании бекапа базы 1С 7.7, на MS SQL Server 2008, получаем ошибку Error: 3041, Severity: 16, State: 1. Check the backup application log, но если запускать утром вручную — выполняется нормально.
Источники:
Error: 3041, Severity: 16, State: 1. Check the backup application log
v7: Не получается создать бекап на сетевой диск
Решение: В нашем случае — начать бекап не позволяла задача CheckDB, выполняющаяся за 5 минут до старта бекапа, и блокирующая базу.
Помог перенос старта задачи на 10 минут, чтобы они не пересекались.
 

Доброго времени суток!
Имеется сервер с настроенным бэкапом баз в ночное время. До недавнего времени все происходило штатно, по расписанию.
Сегодня ночью бэкап баз создан не был.

Логи MSSQLServer говорят следующее:

2017-05-30 03:40:35.18 spid67 BackupDiskFile::CreateMedia: Backup device ‘X:Microsoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLBackupBDBD_backup_name.bak’ failed to create. Operating system error 5(Отказано в доступе.).
2017-05-30 03:40:35.18 Ошибка: 3041, серьезность: 16, состояние: 1.

Системный журнал приложений говорит тоже самое:

BackupDiskFile::CreateMedia: устройству резервного копирования «Х:Microsoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLBackupBDBD_backup_name.bak» не удалось выполнить create. Ошибка операционной системы 5(Отказано в доступе.).

Никаких изменений ни в систему ни в SQLServer не вносилось. Права доступа не изменялись. Подскажите в какую сторону смотреть, куда копать.

Please, Take a look here:
How to troubleshoot «Msg 3041» in SQL Server

Excerpt from page:

Message 3041 is a generic report about the backup failure. To
understand the cause of the error and resolve it, you must use the SQL
Server Error log entries that occur before the 3041 event entry.
Typically, 3041 is preceded by a detailed error message that states
the real reason for the backup failure. The detailed error messages
are written only to the SQL Server error log and to the client
application. The detailed message is not reported in the Application
log in Windows.

Update (After reading @dezso comment)
I’ve seen the «extra error» reported, but I’m not sure that they are related to the backup error. The backup error is dated at 20:31:06, but the «extra error» are dated at 17:53:27, so the extra error happened about 2 hours and 40 minutes before the actual backup error. And these extra error are related to a logon issue.

I don’t think that a logon issue happening at 17:53:27 could result in a backup failing at 20:31:06. So a think that the backup error, and that the «extra error» are unrelated.

I also don’t think that a generic error happening at 17:53:27 could result in a backup failing at 20:31:06 (unless the DB is really big).
@Arviddk report that «my SQL Server backup keeps failing on a lot of the databases» I think it’s safe to assume that «a lot» mean more than 10 DB.
So I think that if a single backup of a single DB take more than 2 hours and 40 minutes, you cant have 10 or 20 DB like that on a single server… or your server will spend it’s life doing only backup. So I assumed that the single backup take a lot less than 2 hours and 40 minutes, so I think that the backup error and the extra error are not related.

And the last «cachestore flush / ‘Bound Trees'» error reported is dated at 06-11-2012 20:30:11, so it’s something happened after the backup error. Anyway a problem related to the cache shouldn’t result in an error (event if it can slow down something).

Some questions
Some questions that could help identify the issue:

• How much time does it take a FULL backup to execute?
• How much time does it take a DIFF backup to execute?
• Does the error happen only on DIFF backup?
• Which percentage of backup does fail? (1%? 10% 50%)
• Maybe you can try to only do FULL backup to check if it’s an issue related to the DIFF backup? (I’ve never done any DIFF backup on SQL Server, I don’t have experience with them)

According to the MS website in the SQL Server log there should be some others error related to the failed backup, but I’m expecting something more near, in time, to the time at which the backup is failing.

SQL Backup Error 3041 – Top Ways to Fix MS SQL Server Error

This blog will provide the complete and easiest way to fix SQL backup error 3041. Simply read the complete article carefully to get rid of this error immediately. Stay tuned!

MS SQL Backup Error 3041 – Know What Exactly it is

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 log, so we can also call it SQL server backup log error 3041.

After understanding about this MS SQL backup error. Now, let’s proceed further to know more about this issue with the help of user’s real-time scenario.

User’s Real-time Scenario

#Query 1: Hi, currently I am working on to resolve this error:

“Error: 3041, Severity: 16, State: 1 BACKUP failed to complete the command BACKUP DATABASE WITH DIFFERENTIAL. Check the backup application log for detailed messages.“

I had a full backup of the database, but somehow I failed earlier today in the morning. I checked the event viewer which also indicates to check the backup application log. So, how to check backup application log? Or any ideas to solve this MS SQL 3041 backup error problem. If yes? then please suggest me. Thank you very much in advance

#Query 2: Backup Error: 3041, Severity: 16, State: 1.

This SQL error 3041 backup failed message prompts after I failed from taking backup. Now, I need an efficient solution to fix this issue. Thanks.

Quick Solution: In some cases, this MS SQL backup error 3041 occurs due to the corruption issues. So, you should check that database is free from any type of corruption.

However, you should check all the configuration changes you have made. Also, be sure to reboot the system every time a new database is added to the server and a full backup is performed after rebooting the local system.

Note: The above-stated solution is not a proficient one to fix SQL server backup failed error 3041. So, in this situation, you can choose an alternative method to get satisfactory results. In the oncoming section, we will discuss the same. Get a quick look:

An Eminent Way to Fix SQL Backup Error 3041 Without Data Loss

After considering the above-mentioned queries we would like to provide you a rapid solution named SQL Backup Recovery. Using this amazing utility, you can easily get rid of this SQL backup error 3041 without data loss.

The tool has an explanatory and understandable interface. O, any user either novice or technical can operate it without taking any expertise help. However, you can download it on any Windows OS machine because it extensively supports all editions of Windows Operating System.

So, let’s proceed ahead to the oncoming section, where we will disclose the steps to fix SQL error 3041 backup failed.

Steps to Resolve SQL Server Backup Failed Error 3041 Issue

Here, in this section, we will disclose the instruction to fix SQL server backup log error 3041. You just have to follow all the steps to execute the procedure. Let’s begin:

Step 1: Download free demo version of the eminent utility by selecting the download button.

Download Now Purchase Now

Step 2: Click Browse button to add SQL Server BAK files. Then, select the version of your SQL backup file.

Step 3: Now, choose the Multiple Backup file options to backup and export multiple BAK files at once.

Step 4: Select the preferred files and click on the Recover button to backup file which is corrupted and showing error.

Step 5: After completion of the scanning and recovering data components process. Opt the desired elements and hit on the Export button.

Step 6: Choose Export to between SQL Server Database and SQL Server Compatible SQL Scripts. And opt Database Authentication option then, add all the details.

Step 7: Click on the required SQL database items and choose export option between with Schema & Data and With only Schema.

Step 8: Press the Export button to export recovered backup file to the SQL Server Database.

Step 9: At last, the application will pop-up a message after successful completion of the backup procedure.

Attention Note: The free download version allows you to export only 25 records. So, it is better to go with the purchase edition of the application.

Concluding Thoughts

How to fix SQL backup error 3041? It is a most commonly asked query by the MS SQL users. SQL server backup failed error 3041 can be occur anytime to anyone. So, by performing the above-suggested solutions, you can fix this SQL error 3041 backup failed without any data loss.

You can find here some of the frequent or common errors faced which manually performing a database backup or an automated maintenance plan or custom backup job failed.

Backup Error: 3041, Severity: 16, State: 1
Backup 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.

Backup Error 3041 is a generic error which is returned when a backup fails. Along with this error, there are additional errors returned and can be found in the SQL Server errorlog. Look for other specific backup errors, which will point the cause of the backup failure.

Below are more specific errors which cause the backup failures.

Error: 18204, Severity: 16, State: 1
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
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 error. – Another issue when this can occur is, if there are any space at the end of the folder name.

Msg 3201, Level 16, State 1, Line 1
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
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 VSSwriter 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
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
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 
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 and 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